Web socket re-connection error on auto email monitoring turned on

Detailed problem:
We auto email monitoring option was enabled in app settings and the websocket is reconnected for some reason or app is restarted, the server will have already running cron agent job for monitoring. But in reconnection the cron scheduler is recalled with same cron id making websocket disconnect.

Fix:
- Add check before calling cron agent scheduler , whether it's already running or not with same id.
- Also when Toggles down the auto email monitoring option then the scheduler should be cancelled, which is not yet implemented.

Structure:
As the auto email monitoring, is made with keeping in mind that the app will be running in background for certain tasks. And the cron agent doesn't get cancelled when the app is closed. So when the app is closed cron agent works in background and notification are send in case of new mails. (+TTS future).

So, here's the structure
- [x] - Remove scheduling of cron agent from chat websocket connection.
- [ ] - In app whenever user logins based on data send from server (previous or default preference of user) call the start cron scheduler api endpoint. (Also add logic to check if existing job is running for same id)
- [ ] - When user turns it off manually from settings call end cron scheduler api endpoint.

Start by tracing the login flow, the auto email monitoring preference, and the cron scheduler API endpoints mentioned in the issue. Verify that reconnecting or restarting does not create a duplicate job for the same cron ID, and that disabling the setting cancels the existing scheduler.

Written by the indexing model from the issue text.