fix: include warning about console and OIDC not being supported together

[jessesimpson36]

Description

Console + OIDC is not supported together until v8.6. This docs update will add a mention of this into our Announcements section of our docs.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[akeller]

@theburi can you review this change? I also see the public issue has two alpha labels - is that correct? If so, this is good to merge.

[jessesimpson36]

@akeller I see from this comment:
https://github.com/camunda/product-hub/issues/2092#issuecomment-2227869728

that alpha3 does not support console SM and that this was pushed to alpha4. therefore, I will remove the alpha3 label from the public issue.

[jessesimpson36]

Actually, @akeller , I see that one is target:alpha3 and the other is version:alpha4. I think perhaps there may be 2 different types of tags to track what a change was intended for vs. what made it in. could someone clarify?

[akeller]

Actually, @akeller , I see that one is target:alpha3 and the other is version:alpha4. I think perhaps there may be 2 different types of tags to track what a change was intended for vs. what made it in. could someone clarify?

@jessesimpson36 we are good. It had two target:alphaX at one point, but it seems to be sorted out now.