Remove Vagrant (unused)

[pdurbin]

What this PR does / why we need it:

We agreed to remove Vagrant in Slack the other day: https://iqss.slack.com/archives/C010LA04BCG/p1692040813846129

I gave the community a chance to weigh in ( https://groups.google.com/g/dataverse-community/c/y1_JCWN44II/m/FFjQTkJ4AwAJ ) but no one seems interested in keeping Vagrant.

Having Vagrant around slows us down when we need to update Payara, Java, or Solr. (For the same reason we removed the Perl installer and docker-aio in the Payara 6 upgrade PR: b829ca7 )

Which issue(s) this PR closes:

• Closes remove Vagrant #9838

Special notes for your reviewer:

I did keep/move the Vagrant version of counter-processor-config.yaml because it might be useful. In the guides we recommend that developers use this file for testing on an EC2 instance.

Suggestions on how to test this:

Make sure the API tests pass.

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

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

Yes, added.

Additional documentation:

None.

[kcondon]

@pdurbin 3 tests failed: https://jenkins.dataverse.org/blue/organizations/jenkins/IQSS-Dataverse-Develop-PR/detail/PR-9839/1/tests

[pdurbin]

@kcondon thanks, yeah, unfortunately, we're seeing some flakiness in our test suite. If you compare with #9835 you'll see similar tests failing:

https://jenkins.dataverse.org/blue/organizations/jenkins/IQSS-Dataverse-Develop-PR/detail/PR-9835/2/tests

I'm 99% sure these are unrelated to Vagrant, which is just a bunch of scripts and docs.

I opened this issue to investigate the failing tests:

• DataversesIT.testMoveDataverse, DataversesIT.testImportDDI, FilesIT.testAccessFacet #9848