Limitador counter storage

**Summary**

Limitador has option to store counters in different places. We should test the durability and share-ability between limitador istances.

**Documentation**

https://github.com/Kuadrant/limitador-operator/blob/main/doc/storage.md

**Additional context**

Currently there is just guide in google disk on global rate limit testing.

I suggest storing the redis connection string in settings.local.yaml simillar to auth0 tests. We can use https://dragonflydb.cloud as redis provider or/and install our own redis as tools via https://github.com/azgabur/kuadrant-helm-install with automatic service discovery simillar as we have for keycloak

**Test cases**

- [ ] Redis
- [ ] Test global rate limiting using redis on multicluster and see the counter is shared https://github.com/Kuadrant/testsuite/pull/731
- [x] Test counter durability on singlecluster when limitador pod is deleted https://github.com/Kuadrant/testsuite/pull/727
- Set RLP with counter 2, window: long one
- Do 1 request
- Delete limitador pod = triggering restart
- Do 2 requests, second should be rate-limited
- [x] Disk - only durability testing https://github.com/Kuadrant/testsuite/pull/727
- [ ] GRL re-synchronisation https://github.com/Kuadrant/testsuite/issues/812
- [ ] Redis Cached https://github.com/Kuadrant/testsuite/issues/813