fix(ldap): escape username filter

# Which Problems Are Solved

The username input to login with LDAP was taken as is without escaping it, which could potentially allow manipulating the filter used to check if the user exists (LDAP injection).

# How the Problems Are Solved

Escape the username when used in the filter.

# Additional Changes

Removed unnecessary parsing of the returned user DN.

# Additional Context

None

(cherry picked from commit 08007da)

fix(ldap): escape username filter

# Which Problems Are Solved

The username input to login with LDAP was taken as is without escaping it, which could potentially allow manipulating the filter used to check if the user exists (LDAP injection).

# How the Problems Are Solved

Escape the username when used in the filter.

# Additional Changes

Removed unnecessary parsing of the returned user DN.

# Additional Context

None

(cherry picked from commit 08007da)

(cherry picked from commit a56d4bf)

chore(deps): update go dependencies (zitadel#12094)

This PR updates all (possible) go dependencies and requires a backport
to v4.x

(cherry picked from commit cc74a36)

chore: update go dependencies (zitadel#11883)

Updates all dependencies to latests versions (apart from the ones where
there are already issues to solve their updates).
Some updates required minor changes.

(cherry picked from commit f94e406)

maintenance branch

feat: add DSN/URL connection string support for PostgreSQL and Redis (z…

…itadel#11729)

fix: enforce organization scopes

# Which Problems Are Solved

- Organization scopes not being enforced in device authorization flow
- No check whether orgs exist in an authorization request

# How the Problems Are Solved

- Logic to get ID/Domain of an organisation is moved to the `Request` interface.
- Added assertion for the org ID/Domain when creating the authorization request.
- Added checks when authorizing the auth / device request with a session to check if a specific organization is enforced.
- Added checks to prevent using a session of a user from another organization if enforces by scope

# Additional Changes

# Additional Context

- Related Issue: zitadel#11160

---------

Co-authored-by: Livio Spring <livio@zitadel.com>
Co-authored-by: Max Peintner <peintnerm@gmail.com>

(cherry picked from commit c3a6bdb)

prevent eventual consistency issues

fix git tag

fix(webauthn): expire invite code by creation date

# Which Problems Are Solved

When an expired invite code was used for webauthn (passkeys), the change date got updated by the failed event. This change date was used to test for expiry, meaning failed events would reset the expiry timeout.

# How the Problems Are Solved

This fix adds a Code Creation Date to the writemodel which gets set by the first event. This can be the added or requested event.

# Additional Changes

- Expiry renamed to CodeExpiry so it's consistent with similar write models using secret codes.
- humanVerifyPasswordlessInitCode takes an algorithm instead of the complete generator, so the method can be unit tested easier
- Added tests that reproduced the original issue

(cherry picked from commit 64ee480)