docs: document org CLI version policy bypass and flag exclusivity

[devin-ai-integration]

Summary

The fern org command family (fern-api/fern#16952) lets an org admin set org-level Fern CLI version bounds — a minimum, a maximum, or an exact pin — that every project follows automatically, so teams with many API repos stop drifting onto different CLI versions and producing inconsistent generated output. The command surface and enforcement behavior are already documented on the CLI version policy and Commands reference pages (#6434); this PR fills the two remaining gaps from the source PR.

• cli-version-policy.mdx: new "Bypass the policy" section covering FERN_IGNORE_ORG_VERSION_BOUNDS=true and the fact that fern org itself is exempt from version redirection (so an admin can always change policy from an out-of-range project). Also names the 2.5s registry timeout in the existing fail-open sentence, and notes that a positional pin can't be combined with --min/--max.
• commands.mdx: same mutual-exclusion note on the fern org set cli-version accordion.

fern check --warnings and Vale pass (remaining Vale warnings are pre-existing latest hits elsewhere in the files).

Link to Devin session: https://app.devin.ai/sessions/4c722e4289234d8387c5f713d43802fe

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

🌿 Preview your docs: https://fern-preview-devin-1785344943-org-version-bounds-details.docs.buildwithfern.com/learn

Here are the markdown pages you've updated:

• learn/cli-api-reference/cli-reference/version-policy
• learn/cli-api-reference/cli-reference/commands