We have deployed this change to GitLab.com and so we no longer need to
switch based on a feature flag or environment variable.
Gitlab::Redis::RateLimiting falls back to Gitlab::Redis::Cache when not
configured, which means that existing self-managed instances will
continue to work correctly.

Changelog: other