Create rpl_master_retry_count.test

[ParadoxV5]

• The Jira issue number for this PR is: MDEV-35304

Description

I created a MTR test to test --master-retry-count (and also master_connect_retry as a dependency) because I suspect its 0 edge case doesn’t match the KB description.
My local build doesn’t have debug_sync so I’m borrowing our buildbot.

Release Notes

N/A (if the edge case I suspected doesn’t apply)

How can this PR be tested?

Neither master_retry_count (MDEV-25674) nor master_connect_retry are global variables, so I had to hardcode them.

Basing the PR against the correct MariaDB version

• This is a new feature or a refactoring, and the PR is based against the main branch.
• This is a bug fix, and the PR is based against the earliest maintained branch in which the bug can be reproduced.

PR quality check

• I checked the CODING_STANDARDS.md file and my PR conforms to this where appropriate.
• For any trivial modifications to the PR, I am ok with the reviewer making the changes themselves.