Reorganize Ingress content

[conceptualshark]

Description

Relates to https://github.com/camunda/developer-experience/issues/199

A quick win for cleaning up some of this content is to add tabs to the combined/separated Ingress instructions. Holding off on any additional content rework and the potential for creating new pages (instead of tabs) is separated out into https://github.com/camunda/developer-experience/issues/367.

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]

Quick win, quick approval 🚀

[github-actions]

🧹 Preview environment for this PR has been torn down.