Fix: Correct YAML frontmatter syntax in Access Analyzer KBs for search indexing

[hilram7]

Problem

Access Analyzer KBs were not appearing in Docusaurus search results despite being properly merged, while Auditor KBs were working correctly.

Root Cause Analysis

After investigation, the issue was inconsistent YAML frontmatter syntax in the `description` field:

• Working KBs (Auditor + some Access Analyzer): `description: >-` (strips trailing newlines)
• Non-working KBs (newer Access Analyzer): `description: >` (preserves trailing newlines)

This subtle YAML syntax difference affects how Algolia search indexes the content.

Evidence

• Auditor KBs work because they use `description: >-`
• Some Access Analyzer KBs work (like `access-analyzer-migrating-low-priority-scheduled-tasks...`) because they also use `description: >-`
• Newer Access Analyzer KBs don't work because they use `description: >` (without the dash)

Solution

Fixed YAML frontmatter syntax in affected Access Analyzer KBs:

• `500-Internal-Server-Error-Using-Okta-SSO-Published-Reports.md` - changed `description: >` to `description: >-`
• `SEEK-warning-DLPEX-Database-Not-Exist.md` - restructured frontmatter to use `description: >-` format

Impact

Once deployed, the previously missing Access Analyzer KBs should appear correctly in both dev and main Docusaurus sites' search results, matching the behavior of working Auditor KBs.

Note

This PR supersedes the previous PR #371 which addressed trailing `---` issues but missed the real root cause.