chore: add config policies to CLI reference docs

[amandavialva01]

Ticket

CM-480

Description

• Add config policies to CLI reference docs
• give det config-policies shorthand name det cp
• clarify in the config-policies help messages that policies are applied globally when --workspace-name flag is unspecified

Test Plan

Checklist

• Changes have been manually QA'd
• New features have been approved by the corresponding PM
• User-facing API changes have the "User-facing API Change" label
• Release notes have been added as a separate file under docs/release-notes/
  See Release Note for details.
• Licenses have been included for new code which was copied and/or modified from any external code

[netlify]

✅ Deploy Preview for determined-ui canceled.

Name	Link
🔨 Latest commit	a5d296c
🔍 Latest deploy log	https://app.netlify.com/sites/determined-ui/deploys/671a6e97f7e87600081fd855

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.47%. Comparing base (22ad457) to head (a5d296c).
Report is 15 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10118      +/-   ##
==========================================
- Coverage   54.49%   54.47%   -0.03%     
==========================================
  Files        1267     1267              
  Lines      159437   159437              
  Branches     3637     3635       -2     
==========================================
- Hits        86885    86850      -35     
- Misses      72419    72454      +35     
  Partials      133      133              

Flag	Coverage Δ
backend	45.66% <ø> (-0.07%)	⬇️
harness	72.55% <ø> (ø)
web	54.02% <ø> (ø)

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

Files with missing lines	Coverage Δ
harness/determined/cli/config_policies.py	16.36% <ø> (ø)

... and 10 files with indirect coverage changes

[kkunapuli]

Order is good.

I don't agree with the reasons for the suggestion though. The config policies will be consistent if set via webUI or CLI whether admins draft them separately or not. That makes it sound like there's a bug in our APIs or something.

I think the reason to suggest admins draft it separately is that our webUI does not support common helpful features like "save", "undo", or any kind of history.

[amandavialva01]

The config policies will be consistent if set via webUI or CLI whether admins draft them separately or not. That makes it sound like there's a bug in our APIs or something.

Hmm, I guess I meant consistency on their end (so that they don't have one config used for the webUI policies and a different folder of configs whose paths are input into the CLI).
but that makes sense! I'll rephrase the benefits of the note

[azhou-determined]

nice