CAMEL-23550: Fix bean lookup in route templates to check local repository

[cunningt]

Summary

Fixes bean lookup in route templates by checking the RouteTemplateContext's local bean repository before falling back to the global registry.

Kamelets defining beans via the beans: section store them in a local bean repository scoped to the RouteTemplateContext. Previously, the AbstractReifier only checked EndpointHelper.resolveReferenceParameter and the global registry, causing NoSuchBeanException when route templates tried to reference their locally-defined beans.

This fix adds a lookup step that checks the local bean repository (if present) before falling back to the global registry, allowing Kamelets to properly reference their own beans.

Affected Components

• Multiple Kamelets in the catalog: protobuf-deserialize-action, protobuf-serialize-action, avro-deserialize-action, avro-serialize-action, data-type-action

Test Plan

• Build passes with mvn clean install
• Integration tests in camel-kamelets project (ProtobufIT) verify the fix

🤖 Generated with Claude Code on behalf of Tom Cunningham

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

[github-actions]

🧪 CI tested the following changed modules:

• core/camel-core-reifier
• core/camel-core

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

⚠️ Some tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• core/camel-core: 2 test(s) disabled on GitHub Actions

Build reactor — dependencies compiled but only changed modules were tested (2 modules)

• Camel :: Core
• Camel :: Core Reifier

---

⚙️ View full build and test results

[apupier]

I think it will be good to add a test case

[cunningt]

Added test cases and made import / instanceof changes