Create a UI for the Disclosures Tab (site-level privacy)

[carike]

Background:

The Disclosures Tab is an initiative that is underway in the Core Privacy Team.
The aim is to help site owners / admins better understand what information their site (plugins, themes and Core) collects, where the information is stored and where it is sent - and in particular, who it is shared with.
We hope to help site owners / admins make more informed privacy choices (e.g. when choosing which plugin to install) and to better understand their risk profile when it comes to privacy.
For the most part, the actual "controlling" is planned for a sibling plugin, the Permissions Tab, which is not currently intended to be merged into Core, as this will contain more advanced settings.
You can read more about the various privacy initiatives here: ​https://make.wordpress.org/core/2020/08/19/minutes-core-privacy-meeting-19-august-2020/

The Challenge:

The reach and impact of privacy initiatives are severely limited when there is no UI for it in /wp-admin/.

The Solution:

This ticket represents one milestone for the Disclosures Tab initiative.
#51092 proposes a .json schema for various Core components (e.g. avatars), for plugins and for themes.
The UI needs to present this information in a digestible format.
It seems preferable to aggregate the information to provide a holistic understanding to the site owner / admin and then allow them to drill-down to a more granular level (e.g. a single plugin).
The description fields in the schema can be used to explain the significance of each item to the site owner / admin.

Create a sub-menu under Settings called "Privacy" (H1).

Create a header called "Disclosures" on the page (H2).

The section below this should be filterable.

This section will eventually contain quite a bit of information, so it may be desirable to split it into tabs to improve the readability of the text.
Suggested tabs: Overview, Core, Plugins, Themes, Blocks.

This ticket was created in response to a request from Paaljoachim.

[azaozz]

Needs designing, both "application design" and UI/UX design.

Also this should be done together with #51092, or perhaps #51092 should be closed as a duplicate as it is part of this feature, not a separate thing.

[hellofromTonya]

With less than 2 weeks left to 5.6 Beta 1, per today's Scrub, punting this ticket. If a component maintainer has capacity to move it towards merge to land in 5.6, that will be great.