[DOCS] Opster Migration: Add errors to troubleshooting pages

[thekofimensah]

• Created a new Errors section in troubleshooting with specific errors inside
• Added to security troubleshooting 2 errors, attempting to follow existing formatting

Attempted to follow https://docs.elastic.dev/content-architecture/content-type/troubleshooting/error

Via discussion with @marciw , this section is still being organized so these may be moved around.

[marciw]

thanks @thekofimensah ! I'll review soon, FYI but these won't be for 9.0 because we don't want to inadvertently introduce build issues right before the release.

also there are 92 build errors (?!) so we'll have to figure out what's up there ;)

[Copilot]

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (4)

troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md:10

• [nitpick] Consider removing or clarifying the placeholder comment to ensure the documentation is clear and professional.

# is mapped_pages needed for newly created docs?

troubleshoot/elasticsearch/security/token-expired.md:10

• [nitpick] Review whether the placeholder comment is necessary; if not, it could be removed to streamline the document.

# is mapped_pages needed for newly created docs?

troubleshoot/elasticsearch/security/invalid-token.md:10

• [nitpick] Consider removing the placeholder comment if it is not intended for the final documentation.

# is mapped_pages needed for newly created docs?

troubleshoot/elasticsearch/failed-to-parse-field-of-type.md:10

• [nitpick] Evaluate whether this placeholder comment should be removed to avoid potential confusion in the final documentation.

# is mapped_pages needed for newly created docs?

[marciw]

also there are 92 build errors (?!) so we'll have to figure out what's up there ;)

I merged in 'main' to fix these. review coming soon ⏳

[marciw]

This is just a first batch of comments -- more coming soon.

[marciw]

Still not done, but sending over another batch of suggestions

[marciw]

btw @thekofimensah , just want to make sure you're aware that every docs PR automatically gets a preview link: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/1116/troubleshoot/elasticsearch/ (look for environments/deployments in the PR history)

This can help with things like figuring out whether to use bash or console

[marciw]

Another batch

[marciw]

Last batch for now. Thanks for working through all my suggestions!

[marciw]

A few more tweaks.

[marciw]

Approving but w/ one more grammar note. Thanks!