Document sharing dynamic access keys with users

[angelodlfrtr]

Add a "Share the Key with Your Users" section to the dynamic access keys page explaining the ssconf:// scheme: how to derive the key from the hosted configuration URL, naming the client entry with a URL fragment, and warnings that the key URL is a credential and that deleting the hosted configuration does not revoke access.

Translate the new section into all 17 locales, keeping code blocks identical to the English source as required by the translation verifier, and drop the now-unneeded verifier exceptions for this page along with a stale entry for vpn/advanced/websockets whose counts already match.

[greptile-apps]

Greptile Summary

The PR documents how operators share dynamic access keys and strengthens translation link validation by replacing broad count exceptions with exact exclusions.

• Explains ssconf:// conversion, display-name fragments, credential handling, and server-side revocation.
• Adds expected translation differences for the new English-only content.
• Preserves URL-by-URL checking after removing explicitly identified English-only links and validates reordered links as a set.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
docs/vpn/management/dynamic-access-keys.md	Adds accurate user-sharing, credential-protection, and revocation guidance for dynamic access keys.
scripts/verify_translations.py	Replaces broad link-count exceptions with exact English-only link exclusions and validates known link swaps without leaving the previously reported URL-checking bypass.

_{Reviews (4): Last reviewed commit: "Validate translated links in docs with k..." | Re-trigger Greptile}

[ohnorobo]

You can delete the translated additions. We don't use machine translation since we're not yet sure it's reliable enough and we're not able to double-check it. We intend to set up a translation pipeline with a vendor later, but for now we just keep new articles in english only.