I60 config discrepancies destroys development data when running specs

[ShanaLMoore]

In this PR, I compared configurations against working apps like hyku proper and UTK, and took note of the configuration discrepancies.

In particular, we were trying to find the reason why running specs would destroy our local data. Specs should rely on its test environment and its data should be separate from development. Using RAILS_ENV=test didn't make a difference.

For specs there's helper method called #reset! It runs in a before suite hook. Within that method, ActiveFedora::Cleaner.clean! triggered the issue of destroying development data.

With LaRitas help we discovered the issue was actually because of solr using hydra-development for both environments.

Issue:

• 🐛 Running specs destroys local data scientist-softserv/ams#60 (comment)

EOD TODO:

• test out changes to confirm that running specs won't cause development data to be destroyed

ref: scientist-softserv#60 (comment)

1. Assuming you have no data, create data in rails console 3.times {Asset.create!}
2. Verify count Asset.count => 3
3. Run the following spec

DEPENDENCIES_TEST=1 bundle exec rspec spec/features/update_admin_data_spec.rb 

4. reload! ; Asset.count => hopefully returns the correct count (ie: 3 in this example)

UPDATE: Tested ✅

In this screenshot, i created 3 assets in rails console. then in the spec context i ran the offensive line that previously deleted development data, reloaded rails c and asked for the count again. Previously it would return 0 but it appears to be persisting now.

[ShanaLMoore]

@orangewolf @aprilrieger I would appreciate a review of this, from a devops perspective. I'm not confident about or totally familiar with the consequences of my changes besides the fact that its no longer destroying my development data when I run a spec 🎉

Also, something weird is still happening. I am able to connect to hyku.test even though it's not listed in the docker-compose file and i should only be using ams.test. This was also the reason why we weren't able to run feature specs locally.

[ShanaLMoore]

Switching to Draft. It's ready for review but I don't want anyone to accidentally merge it until devops review.

[orangewolf]

remove stuff unrelated to this fix. the fix looks great though.