docs: Describe task config policies

[tara-hpe]

Docs Created/Updated

• Add Config Policies Guide
• Update RBAC/Precanned Roles
• Update user accounts

Note: Feature is enterprise only

Description

Test Plan

Scenarios tested with screen captures:

priority_limit

invariant_config

complete example

#example invariant config

Checklist

• Changes have been manually QA'd

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	9929dc8
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/6712bd327e39fd00082e4da9

[johnkim-det]

LGTM

[amandavialva01]

Suggested change

	# Create a new policy
	det policy create <policy_name> --config <policy_config_file.yaml>
	# Set config policies for a given scope.
	det config-policies set <workload_type> --workspace <workspace_name> --config-file <policy_config_file>
	where <workload_type> can be either `experiment` or `ntsc` and <policy_config_file> is the absolute or relative path the YAML or JSON file containing your config policies.
	When creating global config policies, you don't need to specify `--workspace <workspace_name>`

[amandavialva01]

On the note of the <workload_type> being experiment or ntsc I brought up using "NTSC" instead of "Tasks" in the webUI during a demo a couple of weeks ago, and someone (I think Tim?) mentioned that customers aren't very familiar with the NTSC terminology /categorization. If that's the case, it could be worth changing ntsc to tasks in the CLI for consistency (if time permits)!

[amandavialva01]

I think it's also important we use plural "config policies" everywhere!
We should probably mention somewhere in the docs that config policies are set together or not at all (updating config policies with the webUI or CLI will always update both your invariant config and constraints for a given scope, you cannot just update one of the two using our API)

[tara-hpe]

@amandavialva01 changes applied but, keeping this open in case you want to retain your note about the CLI. Do we need to share this with the CLI engineer?

[amandavialva01]

Yes! Saloni was the CLI developer, but she is currently on rotation on a different team! We currently have one ticket left for CLI work that I picked up.
But we have been tackling high priority fixes/work before making other changes. With that being said, I do think the only remaining "bug" fix is in review and a change like this could be made in the CLI ticket I linked (CM-576).
WDYT @kkunapuli ? Should we make this change after comments from the demo two weeks ago?

[amandavialva01]

Looks awesome, Tara, fantastic work!!

[amandavialva01]

Suggested change

	Tasks such as NTSC (notebooks, tensorboards, shells, and commands) and resource managers (RMs)
	Tasks such as NTSC (notebooks, tensorboards, shells, and commands) and experiments