[Feature] [Server/CI]: add Redis authentication caching and build/test workflows

[Gautam25Raj]

Summary

This pull request introduces Redis-backed authentication caching to improve the performance of authentication-related operations and adds automated build and test workflows to strengthen continuous integration and code quality.

What's Changed

Authentication Improvements

• Implemented Redis-based caching for authentication data.
• Improved authentication performance by reducing repeated data lookups.
• Added cache infrastructure to support more efficient user and session retrieval.

Continuous Integration

• Added automated build workflows to validate changes across the project.
• Added test workflows to ensure code quality and prevent regressions.
• Improved the development workflow with automated validation during pull requests and repository updates.

Infrastructure Improvements

• Established a more reliable foundation for authentication services through centralized caching.
• Strengthened the project's CI pipeline to improve development velocity and release confidence.

Notes

• No breaking changes are introduced.
• These changes improve authentication performance and reinforce the project's automated testing and build processes.

Linked Issue

• Fixes [HARDENING]: Production Hardening for Better Auth Session Storage & Rate Limiting #161

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📝 Documentation update
• 🧪 Tests (adding or updating tests)

Checklist

• I have read the CONTRIBUTING.md document.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.