Fixes to open lineage connectors

[mandy-chessell]

Description

The Lineage Integrator OMIS has special support for open lineage events which enables events to be passed between connectors registered with a lineage integration context manager. When the open lineage support was written, there was only one lineage integration context manager per integration daemon server. Now there is potential for multiple lineage integration context manager:

• One when the Lineage Integrator OMIS is explicitly activated in the integration daemon's configuration
• One for each integration group registered with the integration daemon that also has at least one catalog target that is a Lineage Integration Connector.

This fix ensures that an open lineage event passed through the lineage integrator OMIS's REST API is passed to all active lineage integration context managers.

In addition the base class for the open lineage API publsher and open lineage file publisher connectors was not extracting the endpoint correctly from the catalog target if hte catalog target is an asset.

Related Issue(s)

None

Testing

Tested open lineage events pssed into the REST API are pased to a registered OpenLineageFilePublisher connector and written to a folder attached as a catalog target to this connector.

Release Notes & Documentation

No changed needed

Additional notes

None