TIKA-4334 - move tika-pipes out of core

[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 mvn 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]

@nddipiazza what do you think?

[tballison]

I'm converting to draft for now. This is at the "builds on my laptop" stage.

[tballison]

One major difference is that tika-pipes-core now brings in jackson for serialization. We could break that into tika-pipes-serialization, but I'm not sure that buys us much. Also, I have some ideas to just pass through json into pipesParser at some point -- instead of deserializing it from json to POJO and then using Java's native serialization to pass it to the pipes-server where it is then deserialized to POJO. 😭

[nddipiazza]

i am looking into this now.

[tballison]

@nddipiazza any objections/recommendations?

[nddipiazza]

sorry meant to say i approve and i have based my branch on this