Fix issue #24065: add SSO certificate expiration workarounds

[dvdksn]

Enhances the SSO certificate expiration FAQ with practical workarounds for locked-out users.

Changes:

• Added "Workarounds if users are locked out" section with three solutions:
  • Contact Docker Support
  • Use username/password if SSO enforcement is not turned on
  • Maintain a break-glass account (best practice)
• Added prevention guidance about monitoring certificate expiration

This helps administrators handle certificate expiration scenarios more effectively.

Fixes #24065

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	1bb657e
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/69bd3c6abc5d0500088c0d5f
😎 Deploy Preview	https://deploy-preview-24446--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[docker-agent]

Assessment: 🟡 NEEDS ATTENTION

The PR adds helpful workarounds for SSO certificate expiration lockouts, which fills a documentation gap. However, there's a style guide violation that should be addressed for consistency.

[dvdksn]

Thank you for catching the style violation. You're correct that the "Term - Description" format reads like marketing copy and doesn't align with our documentation standards.

I've converted the list to simple descriptive bullets that are more direct and appropriate for technical documentation. The content now follows our style guide's guidance on list formatting.