CAMEL-23864: fix edi-x12-as2 and openapi/server examples after YAML normalization

[ammachado]

Summary

Fixes two camel-jbang-examples integration tests that fail after the YAML canonical-form normalization in 60a70d8. Verified locally against Camel 4.18.2 / Citrus 4.10.1; all 8 workflow suites now pass.

JIRA: CAMEL-23864 (related to CAMEL-23863)

Changes

edi-x12-as2/camel/edi-x12-as2.camel.yaml

• Restored onException into the as2Error routeConfiguration (with the AS2 disposition-FAILED script handler). Normalization had moved it into the route steps, causing Route receivePurchaseOrder has no output processors at startup.
• Fixed ediMessageCharset: charset=US-ASCII → US-ASCII (invalid charset name, IllegalCharsetNameException). Latent since the example was added; only surfaced once the route started correctly.

openapi/server/petstore.camel.yaml

• Restored the restConfiguration block with clientRequestValidation: true and apiContextPath: openapi. It had been deleted, so the spec was no longer served at /openapi and the test received HTTP 404.

ftp example (maintenance)

• Moved runtime dependency declarations from jbang.properties (run.deps) to camel.jbang.dependencies in application.properties (natively supported comma-separated list).

Testing

Ran the full build.yml workflow locally:

ftp/test                                PASS
mqtt/test                               PASS
openapi/server/test                     PASS
openapi/client/test                     PASS
aws/aws-s3-event-based/test             PASS
aws/aws-sqs/test                        PASS
edi-x12-as2/test                        PASS
smart-log-analyzer/first-iteration/test PASS

🤖 Generated with Claude Code