feat(core): add by-name secondary resource lookup on Context

[afalhambra-hivemq]

Adds three typed by-name secondary-resource accessors to Context<P>:

• <R extends HasMetadata> Optional<R> getSecondaryResource(Class<R>, String eventSourceName, ResourceID) (abstract)
• <R extends HasMetadata> Optional<R> getSecondaryResource(Class<R>, String eventSourceName, String name) (default; uses the primary's namespace)
• <R extends HasMetadata> Stream<R> getSecondaryResourcesAsStream(Class<R>, String eventSourceName) (abstract)

Closes #3372

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds new Context APIs for retrieving secondary resources by ResourceID and streaming secondary resources from a specific named event source, with cache-backed fast paths and tests to validate behavior.

Changes:

• Added Context#getSecondaryResource(..., ResourceID) and a convenience overload that infers namespace from the primary resource.
• Added Context#getSecondaryResourcesAsStream(..., eventSourceName) with a ResourceCache fast path for read-cache-after-write consistency.
• Expanded DefaultContextTest to cover cache hit/miss, fallback behavior, cluster-scoped vs namespaced primaries, and workflow-managed missing event sources.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/Context.java	Introduces new public API methods and Javadoc for ResourceID lookups and named event-source streaming.
operator-framework-core/src/main/java/io/javaoperatorsdk/operator/api/reconciler/DefaultContext.java	Implements the new APIs, adds cache/resource-cache fast paths, and refactors missing-event-source handling into a helper.
operator-framework-core/src/test/java/io/javaoperatorsdk/operator/api/reconciler/DefaultContextTest.java	Adds unit tests validating the new APIs and fast-path/fallback behaviors.

[metacosm]

LGTM

[csviri]

Thank you for the PR @afalhambra-hivemq !

Could you pls target 'next' branch so this ends up in next minor release rather than in next patch release.

I was also thinking if we should use ResourceID in the method or simply name and namespace directly it might be less user boilerplate code at the end,or? What do you think?

[xstefank]

LGTM, just please change the target branch and the @since tags. Thanks!

[afalhambra-hivemq]

Thank you for the PR @afalhambra-hivemq !

Could you pls target 'next' branch so this ends up in next minor release rather than in next patch release.

I was also thinking if we should use ResourceID in the method or simply name and namespace directly it might be less user boilerplate code at the end,or? What do you think?

Agree, cleaner and less boilerplate for customers.

Also targeting next branch, and changed @since to 5.4.0 as suggested.