Add write discover fetch event API

[xiaohansong]

What

#21279

To add a new internal API endpoint that workers will call.

How

Implement a new Api and hook it up with the existing configRepository logic. Have to implement a converter helper to translate from API model to protocol model.

Recommended reading order

1. x.java
2. y.python

🚨 User Impact 🚨

This function will not be used at this moment because workers are still calling DB directly. Thus no user impact.

[github-actions]

Airbyte Code Coverage

File	Coverage [86.88%]	🍏
SchedulerHandler.java	94.33%	🍏
CatalogConverter.java	91.85%	🍏
SourceHandler.java	90.83%	🍏
WebBackendConnectionsHandler.java	90.23%	🍏
ConnectionsHandler.java	82.02%	🍏
SourceApiController.java	0%	❌

Total Project Coverage	26.68%	🍏

[pmossman]

@xiaohansong I forgot to submit this review yesterday, sorry about that! Left a few comments and suggestions, let me know what you think of them. I can do another pass when needed, just let me know

[pmossman]

I think the naming of this method is a little confusing compared to the method below it, toProtocol. Perhaps we should rename the method below this to toProtocolConfigured and then this method can be called toProtocol?

At the very least, I would add some javadoc to this method and maybe try to include some guidance on when this method should be used versus the below method which returns a configured catalog

[xiaohansong]

yeah agreed. Mike was mentioning we should work with move team to consolidate these two states, but that was a bit out of scope for this PR/tickets.

[xiaohansong]

@pmossman Ready for you to take another pass!

[pmossman]

This looks good to me, I think @mfsiega-airbyte should take a quick pass as well to make sure I didn't miss anything as this isn't my most familiar area of code

[mfsiega-airbyte]

LGTM!