Fix mysqldump master database

[michel-silva]

Description of the change

This PR #54038 adds the functionality to dump master database when missing binary files. Its a solution to this issue #54028.

But, was checked that when the number of slaves was increased, the replication broken.

This new PR fixes this issue, that occurs when increasing the number of slaves.

[mostafa-rz]

@michel-silva Many thanks for the fix. I tested it again and I can confirm all the issues mentioned here, are solved.

[aoterolorenzo]

Hi @michel-silva,

So sorry for the mess, I completely missed this case. Could you resolve the comflicts? Let's merge this!

[michel-silva]

Hi @aoterolorenzo,

Don't worry. I will resolve the conflicts today and let you know.

Thank for your reply.

[michel-silva]

@aoterolorenzo The conflicts are solved. Could you check please?

[michel-silva]

@aoterolorenzo I updated the PR.. Could you check please?

[aoterolorenzo]

Hi @michel-silva,

Sorry for the delay again: We have been performing several breaking changes for the containers, making debian-12 the default distro for all our containers in automated batches so I just preferred to wait to merge this one, since our internal pipelines auto-generate all the scripts (so acutally I have to reproduce and propose this fix in our internal system, to avoid the pipelines tread down this changes). Please, let me see if I myself can solve the conflicts, and set up the internal code proposal. I will be back to you later

[aoterolorenzo]

The fix is failing due to a linter problem in our internal systems:

libmysql.sh:197:43: warning: Quote this to prevent word splitting. [SC2046]

I'll try to fix it in your branch directly. Will be back later.

[michel-silva]

Hi @aoterolorenzo,

This time was me that delay. Sorry, I was working on a urgent issue.

Thank you for resolve the linter problem and merge the PR.