[HACK] AI API keys: Switch generative content remote based on ai source #16142
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

HACK week. Part of #15372
Description
This PR adds a new implementation of the
GenerativeContentRemoteProtocolviaMerchantGenerativeContentRemote. At the moment uses OpenAI as the only source, but later we'll expand to Anthropic as well.At the moment we just assume that when the feature flag is on, we'll always use the merchant's API key, and when the flag is off, we fallback to the default behavior (AI eligibility checks to use Jetpack as AI source, or none).
Steps to reproduce
Testing information
Screenshots
RELEASE-NOTES.txtif necessary.