MID-9537 Resolve filtered connectorRef for additional connectors

[kay1313]

Summary

Fixes MID-9537: additional connectors failed when their connectorRef was specified using a filter instead of a direct OID.

The primary resource connectorRef already supported filter-based resolution, but ConnectorSpec.Additional still required an OID directly from the resource definition. This caused resource completion to fail with:

Connector OID missing in ConnectorSpec.Additional(...)

Changes

• Added filter-based connector reference resolution in ConnectorManager.

• Reuses the resolved connector OID for cache lookup and connector instance creation.

• Stores the resolved connector OID as transient state in ConnectorSpec.

• Does not mutate the resource connectorRef.

• Does not create or persist repository deltas for the resolved OID.

• Added ConnectorSpec#getConnectorRef() so both main and additional connector specs can expose their backing reference.

• Added regression tests for:

  • primary connectorRef by filter
  • additional connectorRef by filter
  • additional connectorRef by direct OID
  • filter matching no connector
  • filter matching multiple connectors
  • ensuring the old “Connector OID missing” error is not produced

• Added release notes entry.

Testing

Added/updated CSV provisioning tests in AbstractCsvTest.

The tests verify that filter-based additional connector references are resolved internally, remain invisible in the returned resource object, and are not persisted to the repository.