Pass control message to connector builder frontend

[maxi297]

What area the feature impact?

Connectors

Revelant Information

As a connector developer developing for single use refresh token API, I don't want to enter a new refresh token every time I do a test read

Context

Some APIs invalidate the refresh token once it's used (for example, quickbooks and GitLab). The platform and the CDK already have a mechanism to support this where a control message is emitted with the new configuration. We need to replicate this mechanism.

Gap

Today, the connector builder is silencing those messages. We need to return the latest one to the frontend so that it updates its config. In order to do that, we will:

• Return the most recent AirbyteControlConnectorConfigMessage as part of the API
• Frontend will use this information to update it's config

Acceptance criteria

• A connector developer developing for single use refresh token API only needs to enter the refresh token once when opening the connector builder project. Do an example with an API
• Disable testing values menu while request is in flight to avoid race condition

[flash1293]

I'll move this back to the sprint backlog for now as it depends on the refresh token authenticator being available in the UI

[flash1293]

Needs a follow-up (owned by @maxi297 ) - to make sure the most recent config is captured in its entirety, we need a path in the code for components to queue messages for dispatching them later, see #27017

[flash1293]

Un-assigning myself for the next week