Enable dynamic ratelimiting / adjust clamav resource limits

[netomi]

This PR changes the following things:

• increase clamav resource limits (Update clamav service resource limits #8199)
• enable dynamic rate limiting and disable static one
• update to v0.32.2 which includes some small fixes wrt rate limiting

After the rate limiting is enabled, it has to be configured via the admin dashboard.

@chrisguindon suggested to start with the same configuration as now and then gradually adjust limits.

So I added a safety tier with 75 RPS already in the DB:

[chrisguindon]

@chrisguindon suggested to start with the same configuration as now and then gradually adjust limits.

+1

Our first goal is simply to migrate to the new rate-limiting system and confirm that it works as expected.

From there, we will need to work with @JoeTot to define how we want to rollout the free tier and register customers. From my perspective, it's important that we stay aligned with what was shared with the community in my blog post:
https://blogs.eclipse.org/post/christopher-guindon/scaling-open-vsx-registry-responsibly-rate-limiting

For most users, nothing should feel different. Developers should see little to no impact, and publishers should not experience disruption to normal publishing workflows. Sustained, high-volume automated consumers may need to coordinate with the Registry to ensure their usage can be supported reliably over time.

[netomi]

please approve so I can merge and start the deployment