feat(Core): gracefully shutdown router/scheduler if Redis is unavailable

[prajjwalkumar17]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates

Description

The change will from now allow the server to gracefully shutdown once the redis goes down. We are passing the tx and rx using a Oneshot::channel() for redis . It has a suitable receiver to stop the server once the tx is received.

Additional Changes

• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

As the core Server wasn't shutting down whenever redis goes down and rather that going down with it. Server stayed there throwing health is good and then sending errors when hitting other routes.
Now the server gracefully goes down too once the redis goes down

How did you test it?

Tested it manually as we just need to check whether or not the server is shutting down on redis stopping

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[NishantJoshi00]

Hey @prajjwalkumar17, please setup commit verification and enforce it through github