Update C8Run to 8.7.0-alpha3

[akeller]

Description

Per https://camunda.slack.com/archives/C03NFMH4KC6/p1736947708579689.

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]

👋 🤖 🤔 Hello, @akeller! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/self-managed/setup/deploy/local/c8run.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[akeller]

@conceptualshark should this be added to the alpha release manager checklist, or do you want to be responsible for this moving forward? This is one of those topics that I see us eventually automating, but for today will be manual.

[conceptualshark]

@akeller Thank you for catching this! Automation would be great, but I think putting it into the release checklist would be better for now. I don't mind handling it, but I also want to ensure it's put somewhere so it's not forgotten.

Is there any way for us to link to something static in terms of a given release's "latest" here? We've also run into this issue when patching prior releases, so it would be nice to point to a single location.

[hisImminence]

lgtm

Thank you @akeller.

I will add this for now to the C8Run release checklist as well!

[akeller]

@conceptualshark please sync with @hisImminence and team on this. More thoughts in this (brief) thread - https://camunda.slack.com/archives/C03NFMH4KC6/p1736961684034949?thread_ts=1736947708.579689&cid=C03NFMH4KC6