Move PDFBox/Tika PDF native-image configuration from langchain4j-ingest to camel-quarkus-tika

PR #9078 added PDFBox runtime-init/resource registrations and the angus-activation feature exclusion to the langchain4j-ingest deployment processor, classpath-gated on PDFBox. Any camel-quarkus-tika + tika-parser-pdf-module application would benefit from the same configuration, so it should be homed in camel-quarkus-tika (with native coverage using tika-parser-pdf-module in its integration tests) and the ingest processor slimmed accordingly. See the review discussion on #9078.