Controlling the editor: Theme.json settings to disable/enable all block controls.

[youknowriad]

Improve WordPress Editor APIs to allow deeper and systematic control of the block editor’s UI/UX from theme.json and Custom Post Type (CPT) registration—making site-level (theme.json) and granular (CPT-level, pattern level) editor locking first-class, predictable, and testable.

1. The first step required to do this is to unify all the block UI controls under the same paradigm. This has been achieved in Standardize Block Inspector Settings to use ToolsPanel - Tracking Issue #67813 as now all the block inspector settings rely on ToolsPanel

2. The second step here is going to be to audit all theme.json settings and block tools panels and add missing settings to all the block tools panels:

• Enable or disable all inspector controls and toolbar options per block directly via theme.json.
• Ensure all core blocks adhere strictly to these theme.json restrictions.

3. The last step is to ensure this mechanism can be used both at the global level and at a granular level:

• Theme.json is the global level
• We might want CPT registration specific APIs to be able to control these at the CPT level
• Ensure also the "settings" block support allows us to define these restrictions at the "pattern" level.

[justintadlock]

Here's one for the list that's been bugging me:

• Add theme.json method of enabling/disabling support for enhanced pagination #57623