Fix warning about already initialized constants in rake tests within tests

[murny]

Context

Our test output was polluting the console with the following warnings:

/jupiter/lib/tasks/batch_ingest.rake:1: warning: already initialized constant INGEST_REPORTS_LOCATION
/jupiter/lib/tasks/batch_ingest.rake:1: warning: previous definition of INGEST_REPORTS_LOCATION was here
/jupiter/lib/tasks/batch_ingest.rake:2: warning: already initialized constant INDEX_OFFSET
/jupiter/lib/tasks/batch_ingest.rake:2: warning: previous definition of INDEX_OFFSET was here

Appears we were loading the same rake tasks multiple times, which attempts to redefine the CONSTANTS in batch_ingest.rake file.

We can simply just load our rake tasks in our tests in a smarter fashion. Load them once, and don't load them again if they are already loaded.

[murny]

Same code as before, just moved it into the setup block (which will run before each and every test) and only load the tasks if they haven't been loaded before.

This makes the warnings go away as we are not loading the tasks multiple times.

[pgwillia]

👍 LGTM! An elegant solution.

As an aside, the branch wasn't working on my machine initially but it had nothing to do with these particular changes. It had a conflict in the Chromedriver versions. I deleted /usr/bin/chromedriver and then reinstalled with sudo snap refresh chromium