REQUEST: Approver role for @javier-aliaga in dapr/dapr

I would like to nominate @javier-aliaga as an **Approver** on `dapr/dapr`.

Javi has been contributing to the runtime since May 2025 — 40 merged PRs and 83 PRs reviewed in `dapr/dapr`. His work is concentrated in workflows, pub/sub, actors/placement and the CI + release tooling, and he is already one of the most frequent reviewers on runtime PRs in those areas.

Representative contributions:

- [dapr#9844](https://github.com/dapr/dapr/pull/9844): `feat(subscription)`: pause-and-drain pub/sub components on graceful shutdown
- [dapr#10058](https://github.com/dapr/dapr/pull/10058): `fix(wfengine/state)`: fail load on missing history/inbox keys + recoverable retry
- [dapr#10153](https://github.com/dapr/dapr/pull/10153): return `AlreadyExists` when creating a workflow with an active instance ID
- [dapr#9792](https://github.com/dapr/dapr/pull/9792): `fix(pubsub)`: flush bulk subscribe batches immediately via drain-and-flush
- [dapr#9811](https://github.com/dapr/dapr/pull/9811): enable hot reload by default (GA)
- [dapr#9233](https://github.com/dapr/dapr/pull/9233): enable the SQL Server v2 implementation with workflow support
- [dapr#8721](https://github.com/dapr/dapr/pull/8721): custom round-robin implementation for placement raft servers
- [dapr#9584](https://github.com/dapr/dapr/pull/9584): `ci`: version skew integration tests
- [dapr#9294](https://github.com/dapr/dapr/pull/9294), [dapr#9279](https://github.com/dapr/dapr/pull/9279), [dapr#9310](https://github.com/dapr/dapr/pull/9310): traceparent propagation for raw-payload pub/sub, with 1.16/1.17 backports
- All PRs: https://github.com/dapr/dapr/pulls?q=is%3Apr+author%3Ajavier-aliaga
- All reviews: https://github.com/dapr/dapr/pulls?q=is%3Apr+reviewed-by%3Ajavier-aliaga

He is already an approver on `dapr/components-contrib`, `dapr/cli` and `dapr/docs`, a maintainer on `dapr/java-sdk`, and part of the release team — so he consistently sees how runtime changes land across a full release cycle, including backports and version-skew concerns.

Granting approver on `dapr/dapr` matches the review load he is already carrying and reduces the review bottleneck on workflow and pub/sub PRs.

Per [community membership](https://github.com/dapr/community/blob/master/community-membership.md#approver), this needs approving votes from at least two `dapr/dapr` maintainers: @JoshVanL @yaron2 @cicoyle @daixiang0.

Read the approver requirements in community-membership.md, then review the listed dapr/dapr contributions and the current maintainer discussion. Done means at least two dapr/dapr maintainers approve granting @javier-aliaga the Approver role.

Written by the indexing model from the issue text.