Clean up the integration tests of stuff that is never used

[fridrich]

When working on #12871 I realized that there are several unused configuration files and tests some dating from the beginning of this century. So, I made this follow-up commit removing all stuff that is not referenced anywhere. It included even a hardcoded user path on his Mac and several snippets that can mislead someone that is grepping for best practices.

I run the fix through integration tests in embedded and in forked mode, with mimir and without mimir and every time I run them twice, just to be sure there is nothing bombing out on already existing files. The first commit is the actual removal the second commit is the renaming of the tests. So that if one removes test 2 and leaves test 3, there is no gap in the numbering. The diff might be somehow confusing in the renumbering commit, because some tests were bit-to-bit copies, just with different settings.xml.

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
• Run mvn verify to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.
• You have run the Core IT successfully.

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[fridrich]

@elharo do you want to review also these ones?

[elharo]

"I run the fix through integration tests in embedded and in forked mode, with mimir and without mimir and every time I run them twice, just to be sure there is nothing bombing out on already existing files. The first commit is the actual removal the second commit is the renaming of the tests. So that if one removes test 2 and leaves test 3, there is no gap in the numbering. The diff might be somehow confusing in the renumbering commit, because some tests were bit-to-bit copies, just with different settings.xml."

I appreciate the effort, but I think that's making this harder to follow, and I don't think we should rename tests or move files just to keep the numbering intact. That mucks up the history. Can you revert the second commit so this is just about removing files that aren't used and nothing else is touched? Thanks

comments addressed