Define how AI provider plugins are discovered, labeled, and surfaced in Connectors

[jeffpaul]

What problem does this address?

#148 explored bundling additional AI providers directly into the AI plugin.

Since then, the direction has shifted toward:

• the WordPress core Connectors screen (as part of WordPress 7.0)
• individual provider plugins rather than bundled implementations

We do not yet have a defined model for how AI provider plugins could:

• be discovered in the Connectors screen
• be labeled and differentiated (official vs third-party)
• be surfaced from the WordPress.org plugin ecosystem

Some questions to consider as we work through this...

1. Discovery model

• How should providers appear in the Connectors screen?
  • Hardcoded list?
  • WordPress.org Plugins API?
  • Tag-based discovery (e.g. "connector")?

2. Curation and eligibility

• What criteria determine whether a provider appears in Connectors?
• Is there a concept of "featured" or "vetted" providers?

3. Official vs third-party distinction

• How are WordPress-supported providers distinguished from others?
• What labeling is required to avoid user confusion and support burden?

What is your proposed solution?

Some directional signals from prior discussion (see #148 and #27):

• Movement toward individual provider plugins (not bundling)
• Interest in leveraging the WordPress.org plugins API
• Need for clear separation between official and third-party providers
• Potential for AI plugin to prototype this before core adoption

[richardmorrison]

We have just encountered this same issue, and found that at least noting that the user needs to find and install their AI Connector plugin for the functionality to work, would be helpful.
Seeing the "Not Available" greyed out is very unhelpful.
The only reference we found before going through the codebase, was on the WordPress.org plugin page that notes:
"Multi-Provider Support – Works with popular AI providers like OpenAI, Google, and Anthropic."