Compress AI settings page above-the-fold

[Adi-ty]

Move the global AI toggle into the page header and replace the large general settings block with an infotip so Features and Experiments appear higher on the page.

What?

Closes #451

Moves the global “Enable AI” control out of the large General Settings block and into the page header. Replaces the explanatory block with an infotip so the Features and Experiments sections are visible higher on the page.

Why?

The previous layout pushed the main feature sections too far below the fold because the General Settings block consumed a large amount of vertical space. This change keeps the same behavior while improving scanability and reducing the amount of unused space at the top of the settings page.

How?

• Renders the global AI toggle in the page header instead of inside the main DataForm settings section.
• Uses an @wordpress/ui Popover-based infotip to display the explanatory copy.
• Keeps the same settings key and save flow through core-data and the WP settings API.

Use of AI Tools

GPT-5.3-Codex was used to assist with code review and PR description drafting.

Testing Instructions

1. Open the AI settings page in wp-admin.
2. Verify the global AI toggle is shown in the page header.
3. Verify the Features and Experiments sections are visible higher on the page.
4. Hover or focus the infotip icon and confirm the explanatory text appears.
5. Toggle AI on and off and confirm the setting persists after refresh.

Screenshots or screencast

Before	After

Changelog Entry

Changed - Compress the AI settings page above the fold by moving the global AI toggle into the header and replacing the large general settings block with an infotip.

[jeffpaul]

@Adi-ty I see this is in draft, are you still working on this or is this ready for review/testing?

[Adi-ty]

@Adi-ty I see this is in draft, are you still working on this or is this ready for review/testing?

Hi @jeffpaul I've kept it in draft due to the npm ci failures I mentioned in the issue here. There’s a conflict between the new @wordpress/ui and the current @wordpress/build peer dependencies. Since this seems to be a workspace/dependency issue rather than a code one, I wasn't sure if I should mark it ready yet. Thoughts on how we should handle the build mismatch?