fix: use DI for DistributedLockService Redis client (fixes #818)

[menawar]

Overview

This PR addresses issue #818 by replacing the inline new Redis() instantiation in DistributedLockService with NestJS Dependency Injection. This prevents connection leaks on module teardown and improves testability by allowing a mocked client to be passed during unit testing.

Changes

• OrchestrationModule: Created an OrchestrationModule which defines a DISTRIBUTED_LOCK_REDIS provider using the shared Redis factory.
• DistributedLockService:
  • Injected the Redis client via constructor parameter (@Inject(DISTRIBUTED_LOCK_REDIS)).
  • Implemented the OnModuleDestroy lifecycle hook to explicitly close the Redis connection (this.redis.quit()) during module teardown.
• Tests: Refactored distributed-lock.service.spec.ts to pass a mocked Redis client instead of relying on the previously hardcoded Redis class instance.
• AppModule: Registered OrchestrationModule.

Fixes #818

[drips-wave]

@menawar Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[RUKAYAT-CODER]

Well done on the job done so far!
Kindly resolve conflict

[menawar]

Well done on the job done so far! Kindly resolve conflict

thank you @RUKAYAT-CODER conflicts resolved

[RUKAYAT-CODER]

Always pull from main before pushing.
Please fix your workflow to pass.

[RUKAYAT-CODER]

Thank you for contributing to the project.