Bump Spring Boot for Spring SDK to 3.4.x

[akeller]

Description

Based on @aleksander-dytko's comment here.

When should this change go live?

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

PR Checklist

• My changes are for an upcoming minor release and:
  • are in the /docs directory (version 8.8).
  • are in the /versioned_docs/version-8.7/ directory (version 8.7).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[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/reference/supported-environments.md

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

• versioned_docs/version-8.7/reference/supported-environments.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]

We typically announce supported environment changes, but I didn't see anything announced yet despite the version compatibility already being live. This should be added to the 8.7 announcements (which will need to be ported to the 8.7 file in the 8.8 docs too.

[megglos]

Thanks for taking action on this, we need some general mechanism to not forgot about general doc updates that reference these versions + the announcement policy 🤔

Do we have something similar in place anywhere yet? I wonder if we could handle this via some workflows that check for specific lib version changes that are relevant for the docs and at least notify @camunda/tech-writers. wdyt?

[akeller]

Thanks for taking action on this, we need some general mechanism to not forgot about general doc updates that reference these versions + the announcement policy 🤔

Do we have something similar in place anywhere yet? I wonder if we could handle this via some workflows that check for specific lib version changes that are relevant for the docs and at least notify @camunda/tech-writers. wdyt?

We are open to suggestions. We have a few items in our backlog right now:

• Automate updating source links to tagged versions #5082
• Ensure that links to release artifacts are up2date #4908
• Point link in CamundaClientProperties.java to 'stable/8.8' when available #5031
• Reference the latest version + patch for a given version in the docs with a reusable component #5058

Unfortunately, our high workload has us unable to make any progress with this, but my dream is to get this automated and into a reusable component so we only update this in one place and can easily check if it's not right. We'll get there 🙂