feat: add permission for privacy; refactor workspace permissions

[dbouwman]

1. Description:

This PR makes changes to the permissions to address two issues:

• Control the "Privacy Mode" (Tracking Consent - how it works today, vs Privacy Consent - new UX)
• Setup Permissions to enable customers to opt into "Workspace Preview"

To address this, I added

const SystemPermissionPolicies: IPermissionPolicy[] = [
  {
    permission: "hub:feature:privacy", 
    availability: ["alpha"],
    environments: ["qaext"],
  },
  {
    permission: "hub:feature:workspace",  // also replaces temp:workspace:released
    availability: ["alpha"],
    environments: ["devext", "qaext"],
  },
];

In addition, for all Entities (other than Projects), I created a new permission hub:<entity>:workspace, which depends on hub:feature:workspace, centralizing access to all un-released workspaces behind a single permission. I also updates all the other hub:<entity>:workspace:<pane> entries to depend on it's associated hub:<entity>:workspace permission, in addition to any existing dependencies.

PLEASE REVIEW THE CHANGES FOR YOUR ENTITY

I'm pretty sure this will not have any actual impact, and have done a bunch of testing locally, but more sets of eyes is better.

1. Instructions for testing:

• run tests

1. Closes Issues:

• #8199 - privacy permission
• #8200 - workspace preview

1. Updated meaningful TSDoc to methods including Parameters and Returns, see Documentation Guide

2. used semantic commit messages

3. PR title follows semantic commit format (CRITICAL if the title is not in a semantic format, the release automation will not run!)

4. updated peerDependencies as needed. CRITICAL our automated release system can not be counted on to update peerDependencies so we must do it manually in our PRs when needed. See the updating peerDependencies section of the release instructions for more details.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (aab4eda) 100.00% compared to head (7b146f9) 100.00%.
Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master     #1291   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          793       793           
  Lines        14440     14442    +2     
  Branches      2510      2510           
=========================================
+ Hits         14440     14442    +2     

Files	Coverage Δ
...mmon/src/content/_internal/ContentBusinessRules.ts	100.00% <ø> (ø)
.../common/src/groups/_internal/GroupBusinessRules.ts	100.00% <ø> (ø)
...lates/_internal/InitiativeTemplateBusinessRules.ts	100.00% <ø> (ø)
...c/initiatives/_internal/InitiativeBusinessRules.ts	100.00% <ø> (ø)
...es/common/src/pages/_internal/PageBusinessRules.ts	100.00% <ø> (ø)
...es/common/src/permissions/HubPermissionPolicies.ts	100.00% <100.00%> (ø)
...ackages/common/src/permissions/types/Permission.ts	100.00% <100.00%> (ø)
...mon/src/projects/_internal/ProjectBusinessRules.ts	100.00% <ø> (ø)
...es/common/src/sites/_internal/SiteBusinessRules.ts	100.00% <ø> (ø)
...n/src/templates/_internal/TemplateBusinessRules.ts	100.00% <ø> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[juliannemarik]

This looks good for all of collaboration's entities 👍

[juliannemarik]

is adding environments here redundant since they're on the hub:feature:workspace system permission policy?

[dbouwman]

It is, but I wanted to limit my changes to "adding" vs changing... Teams should be curating these permissions as we move towards release, and we may push gating down from hub:feature:workspace to individual panes.