Private APIs: Remove design system packages from packages using private APIs

[aduth]

What?

Updates @wordpress/private-apis internal list of packages using private APIs to reflect the fact that @wordpress/theme and @wordpress/ui no longer use private APIs.

Follow-up to: #78958 (comment)

Why?

This list should reflect the current reality of packages using private APIs.

Tracking issue for @wordpress/ui removing private APIs: #75319

#78958 removed API locking from @wordpress/theme.

Timing-wise, this also pairs well with ongoing stabilization of the theme package , which was promoted to a stable package in #80049.

Testing Instructions

I suppose you could try to use the lock or unlock mechanism with this package name and verify that it no longer allows you to lock or unlock.

Use of AI Tools

No AI was used.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: aduth <aduth@git.wordpress.org>
Co-authored-by: ciampo <mciampini@git.wordpress.org>
Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Size Change: -5 B (0%)

Total Size: 7.71 MB

📦 View Changed

Filename	Size	Change
build/scripts/private-apis/index.min.js	1.13 kB	-5 B (-0.44%)

_{compressed-size-action}

[ciampo]

Nice clean up 🚀

[jsnajdr]

I'd rather use the ### Deprecations header here. That's a better description, even if we're not literally doing a typical API deprecation. "Code Quality" are usually internal refactorings that are invisible to the consumer.

[ciampo]

I also wouldn't add the new entry under "Code Quality", but I would choose "Internal" instead

[ciampo]

Actually, wait a moment — the theme package is still using private APIs at this time

[ciampo]

I just realized that, after the changes from #79594 and #79620, both @wordpress/ui and @wordpress/theme still use private APIs. We will be able to remove the ThemeProvider private export/import starting from WordPress 7.3.

I believe we can close this PR for now.

[aduth]

Good catch @ciampo 🙏 I was unquestioningly catching up on my backlog task in #78958 (comment) and neglected to consider the partial revert that came later. Thanks for flagging that, and let's plan to revisit this once we can remove that compatibility layer.

Glad to see that the tests caught it as well.