SentinelManagedConnection searches for new master upon connection failure (#3560)

[ManelCoutinhoSensei]

Pull Request check-list

Please make sure to review and check all of these items:

• Do tests and lints pass with this change?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Fixes #3560. It should be reviewed after merging #3596

[petyaslavova]

Hi @ManelCoutinhoSensei, thank you for your contribution! We’ll review your change soon(after PR #3596 :) ).

[ManelCoutinhoSensei]

It's been 2 months... do you have any updates @petyaslavova ?

[petyaslavova]

Hi @ManelCoutinhoSensei,
Apologies for the late response. I’ve reviewed the code and added a few comments.

[petyaslavova]

@ManelCoutinhoSensei, please check why tests are failing.

[ManelCoutinhoSensei]

Hi @petyaslavova , besides the one workflow that fails due to having the same name as another, all tests seem to pass here
I've noticed that some of them are flaky but I think that it is not due to my changes (since my main branch synced with this repo's master also fails sometimes)