fix: expand storage operations docs into canonical runbooks

[yeongseon]

Finding

Storage Operations pages are currently too shallow for day-2 operational use and do not follow the repository's Operations template.

Example:

• docs/operations/manage-containers-and-shares.md:10-43 provides a short comparison table, a diagram, and a checklist.
• It then jumps to See Also and Sources (:44-52) without ## Prerequisites, ## When to Use, ## Procedure, ## Verification, or ## Rollback / Troubleshooting.

Repository-wide scan:

• All 10 files under docs/operations/ are missing one or more required Operations template sections.
• The broader Platform/Best Practices/Operations audit found 31 docs without content_validation metadata, including generated/index pages.

Why this matters

Storage operations often affect access, retention, lifecycle, and recovery. Operators need procedural steps, expected outputs, and rollback/troubleshooting guidance, not only a checklist.

Suggested fix

• Rewrite Operations pages as canonical runbooks.
• Include Azure CLI examples, verification commands, expected evidence, and rollback/troubleshooting notes.
• Add content_validation metadata for factual claims and regenerate the validation dashboard.