docs: product roadmap and zitadel versions (#9838)

# Which Problems Are Solved

The current public roadmap can be hard to understand for customers and
it doesn't show the timelines for the different versions. which results
in a lot of requests.
It only outlines what is already fixed on the timeline, but doesn't give
any possibilities to outline future topics / features, which not yet
have a timeline

# How the Problems Are Solved

A new roadmap page is added
- Outline for each version when it will have which state
- Outline different zitadel versions with its features, deprecations,
breaking changes, etc.
- Show future topics, which are not yet on the roadmap

docs/docs/guides/integrate/actions/usage.md

@@ -371,7 +371,7 @@ The API documentation to create a target can be found [here](/apis/resources/act
 To ensure the integrity of request content, each call includes a 'ZITADEL-Signature' in the headers. This header contains an HMAC value computed from the request content and a timestamp, which can be used to time out requests. The logic for this process is provided in 'pkg/actions/signing.go'. The goal is to verify that the HMAC value in the header matches the HMAC value computed by the Target, ensuring that the sent and received requests are identical.
 
 Each Target resource now contains also a Signing Key, which gets generated and returned when a Target is [created](/apis/resources/action_service_v2/action-service-create-target),
-and can also be newly generated when a Target is [patched](/apis/resources/action_service_v2/action-service-patch-target).
+and can also be newly generated when a Target is [patched](/apis/resources/action_service_v2/action-service-update-target).
 
 For an example on how to check the signature, [refer to the example](/guides/integrate/actions/testing-request-signature).