chore(camel-test-infra-docling): upgrade docling.container to v1.30.0

[github-actions]

This PR updates the docling.container container image to version v1.30.0.

Update Details

• Property: docling.container
• Image: quay.io/docling-project/docling-serve
• File: /home/runner/work/camel/camel/test-infra/camel-test-infra-docling/src/main/resources/org/apache/camel/test/infra/docling/services/container.properties
• Old version: v1.29.0
• New version: v1.30.0

Verification

Please verify:

• Container image version is compatible with existing tests
• No breaking changes in the updated version
• Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-docling

Then test the impacted components.

---

This PR was automatically created by the Container Version Upgrade workflow.

[gnodet]

❌ Local IT results for 677672a10f6

Integration test failures detected

Test-infra module: camel-test-infra-docling
Components tested: camel-ai/camel-docling

Summary

ITs run: 49 | Failures: 2 | Errors: 5 | Passed: 42

🔴 Behavioral change (upgrade-related)

OcrExtractionIT.testOcrWithMultipleTextBlocks — Docling v1.30.0 now includes page furniture (footer text) in the default body export. The test explicitly documented and pinned the previous behavior where footer text was excluded. The test comment says: "it will start failing if a future docling release includes page furniture in the body export, prompting us to revisit the limitation" — this is now happening.

This is a user-visible behavior change: the camel-docling component will now return footer/header text that was previously excluded. This needs human review to determine if the test assertion should simply be flipped, or if the component should filter page furniture at the Camel level.

⚠️ Timeouts (likely resource constraints, not upgrade-related)

The following 5 tests failed with HttpTimeoutException: request timed out — the docling container is very resource-heavy (AI model) and these likely reflect local machine constraints rather than behavioral changes:

• ExtractStructuredDataIT.extractStructuredDataFromInvoice
• MetadataExtractionIT.testMetadataExtractionFromPdf
• MetadataExtractionIT.testMetadataExtractionFromUrl
• DoclingServeProducerIT.testJsonConversionOfInvoice
• DoclingServeProducerIT.testAsyncUrlConversion

⚠️ Probable timeout casualty

• ChunkingIT.chunkHybridFromPdf — returned null body (likely due to container being overwhelmed by concurrent requests)

Full test output summary

Tests run: 49, Failures: 2, Errors: 5, Skipped: 0

Failures:
  ChunkingIT.chunkHybridFromPdf:119 — Expecting actual not to be null
  OcrExtractionIT.testOcrWithMultipleTextBlocks:189 — Footer text is page furniture
    and is excluded from the docling body export (but now IS included in v1.30.0)

Errors (all timeouts):
  DoclingServeProducerIT.testAsyncUrlConversion — async conversion timed out
  DoclingServeProducerIT.testJsonConversionOfInvoice — request timed out
  ExtractStructuredDataIT.extractStructuredDataFromInvoice — request timed out
  MetadataExtractionIT.testMetadataExtractionFromPdf — request timed out
  MetadataExtractionIT.testMetadataExtractionFromUrl — request timed out

Local integration tests run by ForgeBot on behalf of @gnodet
Tests run without -Dci.env.name to include ITs disabled on GitHub Actions CI

[gnodet]

❌ Local IT results for 677672a10f6e

Behavioral change detected in docling v1.30.0 — page furniture (footers) are now included in body export.

Test-infra module: camel-test-infra-docling
Components tested: camel-docling

Component	Tests	Passed	Failed	Errors	Skipped	Status
camel-docling	9	6	1	2	0	❌ behavioral change + timeouts

Behavioral change (requires human review)

OcrExtractionIT.testOcrWithMultipleTextBlocks — FAILS because docling v1.30.0 now includes page furniture (footer text) in the body export.

The test at line 182-190 was explicitly designed as a detection assertion for this exact change:

// This assertion documents and pins that behavior; it will start failing if a
// future docling release includes page furniture in the body export, prompting us to revisit the limitation.
boolean foundFooter = resultLower.contains("footer");
assertFalse(foundFooter, "Footer text is page furniture and is excluded from the docling body export...");

The result now contains: "This is the first paragraph with multiple lines of text / Second paragraph starts here containing more information / Footer: Apache Camel Docling Component" — the footer IS present.

Impact: This is a user-visible behavioral change. Previously, docling's body export (Markdown/text/HTML) excluded the FURNITURE content layer (headers/footers). Version v1.30.0 includes it. Camel users processing scanned documents will now see header/footer text in their output.

Recommended actions:

1. Update the test assertion to expect the new behavior (footer text present)
2. Update documentation in docling-component.adoc regarding the "OCR and page headers/footers" note
3. Consider whether this requires an upgrade guide entry

Resource constraint timeouts (not container-related)

• OcrExtractionIT.testOcrJsonConversionFromImage — HttpTimeoutException: request timed out (121.5s)
• ExtractStructuredDataIT.extractStructuredDataFromInvoice — HttpTimeoutException: request timed out (122.7s)
• Fork timeout prevented ChunkingIT from running

These timeouts are due to the heavy AI model container under resource constraints, not behavioral changes.

Local integration tests run by ForgeBot on behalf of @gnodet
Tests run without -Dci.env.name to include ITs disabled on GitHub Actions CI