build(deps): bump tika.version from 3.3.0 to 4.0.0

[dependabot]

Bumps tika.version from 3.3.0 to 4.0.0.
Updates org.apache.tika:tika-core from 3.3.0 to 4.0.0

Changelog

Sourced from org.apache.tika:tika-core's changelog.

Release 4.1.0 - unreleased

• Pipes IPC: carry inline document bytes as a raw binary field beside the tuple in the request envelope -- never inside the tuple or its ParseContext -- and disable Smile's 7-bit binary encoding. Tuple JSON serialized by 4.0.0 with an "inline-bytes" parse-context entry no longer loads; it is rejected with a tailored message (TIKA-4829).

• Digesting embedded documents no longer buffers each embedded object to a temp file. Zip entries are re-read from the parent archive on rewind, and a new process-wide CacheMemoryBudget (seeded by the pipes forked server; default 256MB, clamped to a quarter of the fork's heap; tunable via -Dtika.pipes.cacheMemoryBudgetBytes in the config's forkedJvmArgs, <=0 disables) lets embedded objects stay in memory past the per-object 1MB threshold. New public API on TikaInputStream: get(IOSupplier,...), enableRewind(CacheMemoryBudget), getSeekableByteChannel(). Zip/7z/epub/odf parsing and zip container detection now read through seekable channels, so after detection/parsing a TikaInputStream may no longer be file-backed (hasFile() false); getPath()/getFile() still work and spool on demand (TIKA-4828).

• Pipes now carries the caller-supplied Content-Type across the worker's fresh-metadata boundary as a soft detection hint, so every forked-parse endpoint (/tika, /meta, /rmeta, /unpack, /async, /pipes, plus tika-grpc and embedded PipesForkParser) can route on a client Content-Type, not only on the filename. Detection keeps the hint only when it equals or specializes the content-detected type (e.g. refining image/tiff to image/x-canon-cr2); for bytes with no magic it can select any type, matching the routing power the filename already had. The CONTENT_TYPE_USER_OVERRIDE key is deliberately not carried, so the hint cannot force an unrelated type (TIKA-4825).

• OneNote extraction now follows document order, omits superseded page revisions, sorts author metadata, extracts embedded object BLOBs, and bounds malformed-input recursion and file-derived allocations. Parse warnings and embedded relationship IDs are exposed in metadata. Malformed or truncated files that cannot be fully parsed, and files whose walk yields no content, now fall back to the legacy string dump instead of failing or returning empty output. The legacy MS-ONESTORE walker bounds its recursion (depth caps plus file-node-list and fragment-chain cycle guards) and now honors shouldParseEmbedded for embedded file data (TIKA-4814).

• RawTiffParser extracts the camera-generated JPEG previews embedded in TIFF-based raw images (Nikon NEF/NRW, Sony ARW/SRF/SR2, Pentax PEF/PTX, Adobe DNG and Canon CR2, including BigTIFF DNG containers) as thumbnail embedded documents. image/x-raw-{nikon,sony,pentax,adobe} are now sub-classes of image/tiff, so a named NEF/ARW/PEF/DNG that used to detect as image/tiff (TiffParser, metadata only) now detects as image/x-raw-* and emits thumbnail-N.jpg attachments in /rmeta and /unpack; CR2 keeps its

... (truncated)

Commits

• 514e1b3 [maven-release-plugin] prepare release 4.0.0-rc1
• 4e39e07 revert second rc1 attempt
• 7975986 javadocs take 42
• 95d4235 [maven-release-plugin] prepare for next development iteration
• 666289b [maven-release-plugin] prepare release 4.0.0-rc1
• c9f6585 TIKA-4808 - revert aborted 4.0.0-rc1 release commits; fix per-module javadoc ...
• 41183e7 [maven-release-plugin] prepare for next development iteration
• 5dd7fc7 [maven-release-plugin] prepare release 4.0.0-rc1
• 4b231cf TIKA-4808 -- prep CHANGES.txt for release
• 532a685 TIKA-4808 - remove access to the network parser from cli (#3036)
• Additional commits viewable in compare view

Updates org.apache.tika:tika-parsers-standard-package from 3.3.0 to 4.0.0

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[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.}