refactor(idempotency): replace Redis name with Cache and add valkey-glide support

[leandrodamascena]

Issue number: #6666

Summary

This PR implements an alias from RedisCachePersistenceLayer to CachePersistenceLayer. This change aligns our naming convention with the Powertools TypeScript implementation.

This change improves naming consistency across Powertools implementations while highlighting Valkey-glide library, which brings significant performance optimizations for cache operations. These optimizations improve response times and resource utilization when using the cache persistence layer.

Changes

• Added CachePersistenceLayer class as an alias to RedisCachePersistenceLayer
• Updated documentation to use the new class name
• Included Valkey Glide examples as the primary implementation reference
• Maintained backward compatibility with the original class name

User experience

import os
from dataclasses import dataclass, field
from uuid import uuid4

from glide import GlideClient, GlideClientConfiguration, NodeAddress

from aws_lambda_powertools.utilities.idempotency import (
    idempotent,
)
from aws_lambda_powertools.utilities.idempotency.persistence.cache import (
    CachePersistenceLayer,
)
from aws_lambda_powertools.utilities.typing import LambdaContext

cache_endpoint = os.getenv("CACHE_CLUSTER_ENDPOINT", "localhost")
client_config = GlideClientConfiguration(
    addresses=[
        NodeAddress(
            host="localhost",
            port=6379,
        ),
    ],
)
client = GlideClient.create(config=client_config)

persistence_layer = CachePersistenceLayer(client=client)  # type: ignore[arg-type]


@dataclass
class Payment:
    user_id: str
    product_id: str
    payment_id: str = field(default_factory=lambda: f"{uuid4()}")


class PaymentError(Exception): ...


@idempotent(persistence_store=persistence_layer)
def lambda_handler(event: dict, context: LambdaContext):
    try:
        payment: Payment = create_subscription_payment(event)
        return {
            "payment_id": payment.payment_id,
            "message": "success",
            "statusCode": 200,
        }
    except Exception as exc:
        raise PaymentError(f"Error creating payment {str(exc)}")


def create_subscription_payment(event: dict) -> Payment:
    return Payment(**event)

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 2 lines in your changes missing coverage. Please review.

Project coverage is 96.09%. Comparing base (56a70cf) to head (1f4935a).
Report is 1 commits behind head on develop.

Files with missing lines	Patch %	Lines
...ertools/utilities/idempotency/persistence/cache.py	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6685      +/-   ##
===========================================
- Coverage    96.11%   96.09%   -0.02%     
===========================================
  Files          253      254       +1     
  Lines        12170    12177       +7     
  Branches       904      904              
===========================================
+ Hits         11697    11702       +5     
- Misses         371      373       +2     
  Partials       102      102              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[anafalcao]

APPROVED!