Private and Experimental APIs: Tracking issue

[adamziel]

Shaping the private exports and public experiments APIs:

• Restrict private Block.json and Theme.json APIs usage to Gutenberg plugin #47741
• Separate Private APIs from Experimental APIs #47785
• Private APIs: Improve the unlocking mechanism when paired with data stores #47830
• Developer Experience: There's ~280 __experimental APIs. Let's stabilize them! #40316
• Support private selectors and actions for stores registered via registry.registerStore() and for sub registries. #47421
• Experiments: sharing private APIs with lock() and unlock() #46131
• Private experimental cross-module selectors and actions #44521
• Declare blocks as __experimental in block.json to automate syncing Gutenberg packages to WordPress #40655

[gziolo]

One more item to consider when unlocking selectors and actions from data stores: #47830.

It's based on the refactoring applied in #47375.

Aside: I'm not sure whether [Type] Experimental fits well for this issue. I saw there is an intent to rename the package to emphasize the concept of private APIs, so maybe we should create a label to capture it - either as a feature or package name.