Feature/294 clear test datasets

[ekraffmiller]

What this PR does / why we need it:

Deletes test datasets before e2e tests, so that destroyAll() doesn't fail when trying to delete too many tests at once.

Which issue(s) this PR closes:

• Closes Clear test datasets before integration test  #294

Special notes for your reviewer:

Suggestions on how to test this:

Run the e2e tests, check that test datasets have been deleted after the tests run. Check that "gets the total dataset count" test in DatasetJSDataverseRepository.spec.ts runs without errors

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

no

Is there a release notes update needed for this change?:

Additional documentation:

[MellyGray]

We're also creating datasets in the FileJSDataverseRepository.spec.ts and Collection.spec.tsx files. We should include the destroyAll method there as well.

Additionally, since we're now destroying all datasets at the beginning of each test, we should consider removing all calls to the destroyAll method within the individual tests. Such as in cy.wrap(DatasetHelper.destroyAll().then(() => DatasetHelper.createWithTitle(title)))

[coveralls]

coverage: 97.694%. remained the same
when pulling d32bb54 on feature/294-clear-test-datasets
into 3aa4685 on develop.

[ekraffmiller]

thanks @MellyGray, I made the changes you suggested

[MellyGray]

LGTM!

[g-saracca]

Hi @ekraffmiller , 2 suites of tests are failing, I attach screenshots.
I removed images and volumes from docker, downloaded everything again and they are still occurring in the same way.

[ekraffmiller]

@GermanSaracca I tried it again locally, as well as re-running the action, and I haven't reproduced the errors. I think it must be a timing issue. One thing that may be different is the Docker settings. A while ago, I had to increase my resource settings in Docker, in order to run other containers. Here is what I have for Docker resources:

Can you check what you have, and maybe try running again with more memory?

[g-saracca]

I unassign me from possible local environment problems to test this issue. Looks like a timing issue on my end.
@MellyGray @GPortas could any of you test this on your end?

[GPortas]

@ekraffmiller Can you please resolve the merge conflicts?