TIKA-4715 - try to fix osgi integration tests

[tballison]

Thanks for your contribution to Apache Tika! Your help is appreciated!

Before opening the pull request, please verify that

• there is an open issue on the Tika issue tracker which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
• the issue ID (TIKA-XXXX)
  • is referenced in the title of the pull request
  • and placed in front of your commit messages surrounded by square brackets ([TIKA-XXXX] Issue or pull request title)
• commits are squashed into a single one (or few commits for larger changes)
• Tika is successfully built and unit tests pass by running ./mvnw clean test
• there should be no conflicts when merging the pull request branch into the recent main branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled main branch
• if you add new module that downstream users will depend upon add it to relevant group in tika-bom/pom.xml.

We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the Tika mailing list. Thanks!

[tballison]

@kwin This is claude's effort try to get our osgi integration tests working again. Some have been disabled since 2017.

Is this better than nothing? Is this heading in the right direction? Are there simpler ways to write osgi integration tests?

[kwin]

I think using https://ops4j.github.io/pax-exam/ is easier than just using Felix standalone. That already provides helpers to install bundles and has different options for forking. At Apache Jackrabbit there is e.g. https://github.com/apache/jackrabbit-oak/tree/trunk/oak-it-osgi which is probably similar to what you want to achieve.