Changes for integration tests

[davidblasby]

This does the following:

1. Set the integration test's elastic so it will NOT give low disk watermark error messages and refuse to start if your disk is >90% full.

   • for core/
   • for services/

2. Set services so that it runs on a single JVM. This was because elastic is shared between all the different test cases - some tests were modifying the data at the same time (cf Formatter / Use portal filter #8263), causing inconsistencies as to the uuid of metadata record id=100.

• this could cause some slow downs during the integration tests for services/. However, the slowdown was very small on my local computer. This is something to keep an eye on.

3. One of the integration tests KeywordsApiTest#testImportOntologyToSkos uploaded a file - this would be written (by the ThesaurusManager) to the file system (WEB-INF). On the next run, the test would give an error saying the thesaurus already exisits

• I've added some cleanup code to this test case.

This is problematic on development machines with low disk available (>90% full), and quite difficult to remedy.

I suspect that this hasn't been noticed because the build server;

1. has enough disk space (<90% full)
2. only runs the integration tests once (the added thesaurus isn't visible on the first run because WEB-INF is clean)
3. Formatter / Use portal filter #8263 hasn't been merged yet.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[davidblasby]

elastic doc on this option:
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/modules-cluster.html