Onboarding and settings refactor to React

[jeffpaul]

Is your enhancement related to a problem? Please describe.

The new user experience for onboarding and settings pages was released in 2.1.0, but could be more easily extended as we add new service providers, new features, and even more so when we add a new service provider for an existing feature. This tracking issue will cover the refactoring to React for the onboarding/settings experiences. We'll also want to reduce the heavy, primary references to service providers during onboarding and more on the specific feature being enabled/configured. We can include a note in the UI to the effect of "Powered by " and only force a user to consider which service provider to select if there are multiple to choose from for a given feature.

On top of this refactoring, we'll also want to consider the following items as related requirements to this work:

• Split OCR processing into its own settings #306
• Ensure all required options are in new onboarding #449
• Ability to filter desired terms #50

Designs

TBD

Describe alternatives you've considered

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[dkotter]

Nice guide that we may learn from as far as how to use the built-in WordPress React components for settings pages: https://developer.wordpress.org/news/2024/03/26/how-to-use-wordpress-react-components-for-plugin-pages/

[dkotter]

Another guide around using custom SlotFills may be helpful: https://developer.wordpress.org/news/2024/03/26/how-to-use-wordpress-react-components-for-plugin-pages/#setting-up-the-menu-and-settings-page

[jeffpaul]

Noting that as part of this, it would be good to assess the WP Core WIP Admin update Figma to see where there are missing components/etc in those designs compared to what we're planning for ClassifAI's settings refactor.