CAMEL-23153 - Camel-Google: Add Google Cloud Vision AI component

[oscerd]

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[gnodet]

GoogleCloudVisionConfiguration has both:

• String operation (UriPath — set from the URI remaining, e.g., google-vision:labelDetection)
• GoogleCloudVisionOperations operationType (UriParam — typed enum)

In GoogleCloudVisionProducer.determineOperation() (line 167-183), the logic is:

1. Check message header
2. Check operationType (enum)
3. Check operation (string) → parse to enum via valueOf()

The operation UriPath is always set by GoogleCloudVisionComponent.createEndpoint() (line 47: configurationCopy.setOperation(remaining)), but it's the string name of the
operation, not a separate concept. So operationType and operation represent the same thing in two different types. This is confusing for users — they might set both, and
precedence is unclear.

Suggestion: Either remove operationType and just use the operation string (parsed to enum internally), or make operation a GoogleCloudVisionOperations UriPath (like other Camel components that use enums in the path). Having both is a source of confusion.

I'll push a commit to fix along with other minor issues.

[oscerd]

yarn gulp failures are unrelated