[Workspace] Add privacy levels to the workspace

[Kapian1234]

Description

Add workspace privacy settings to configure user permissions at workspace create, details and collaborators page;
Validate the collaborator input, a single '*' input is not allowed.

Issues Resolved

Screenshot

Workspace create

Collaborators

Workspace details

Disallow '*' as an input

Testing the changes

Changelog

• feat: Add privacy levels to the workspace

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.97%. Comparing base (40e61c7) to head (01f0c85).
Report is 8 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8907      +/-   ##
==========================================
+ Coverage   60.93%   60.97%   +0.03%     
==========================================
  Files        3809     3812       +3     
  Lines       91267    91348      +81     
  Branches    14413    14433      +20     
==========================================
+ Hits        55616    55698      +82     
+ Misses      32097    32096       -1     
  Partials     3554     3554              

Flag	Coverage Δ
Linux_1	29.05% <100.00%> (+0.08%)	⬆️
Linux_2	56.45% <ø> (ø)
Linux_3	37.97% <ø> (+<0.01%)	⬆️
Linux_4	29.03% <ø> (ø)
Windows_1	29.07% <100.00%> (+0.08%)	⬆️
Windows_2	56.40% <ø> (ø)
Windows_3	37.97% <ø> (ø)
Windows_4	29.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[SuZhou-Joe]

@Kapian1234 Snapshot check failed in ci group 3, could you please fix that?

[wanglam]

Can we use style={{ whiteSpace: 'pre-line' }} here? Then we can remove the src/plugins/workspace/public/components/workspace_form/workspace_privacy_flyout.scss file.

[wanglam]

Could you add some unit tests for this file?

[ruanyl]

Should it actually check privacyType2TextMap[privacyType] here?

Suggested change

	{privacyType && <EuiText size="xs">{privacyType2TextMap[privacyType].title}</EuiText>}
	{privacyType2TextMap[privacyType] && <EuiText size="xs">{privacyType2TextMap[privacyType].title}</EuiText>}

[wanglam]

From a type-safe perspective, we don't need to perform any checks here. The privacyType was defined as the WorkspacePrivacyItemType type above. The privacyType2TextMap is using WorkspacePrivacyItemType as the map key. The privacyType2TextMap[privacyType] must exist. Do you think if we should check privacyType2TextMap[privacyType] exists here? It can be updated in the next collaborators' flyout PR.

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/OpenSearch-Dashboards/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/OpenSearch-Dashboards/backport-2.x
# Create a new branch
git switch --create backport/backport-8907-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 8d98654edee51417a640c2fcedf244dc267bddd4
# Push it to GitHub
git push --set-upstream origin backport/backport-8907-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/OpenSearch-Dashboards/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-8907-to-2.x.