Allow seperated Jobs/CronJobs for binlog uploads

[mhkarimi1383]

What

For BinLog uploads we are currently using the same Job as backups (What I understood)

But, What if My cluster goes down and Before That job, And I need that data

How

Being able to set a separated job for uploads of BinLogs (For example I want a full backup at 01:00 AM and I want to upload my BinLogs every 5 minutes) or uploading binlogs contentiously using the agent

In CloudNativePG and Barman Cloud we have this scenerio were we take full backups every night and we are uploading WAL files contentiously to the Object storage

Checklist

• Finish implementation of the issue
• Test all functions
• Have enough logs to trace activities
• Notify developers of necessary actions

[ymmt2005]

Not uploading binlogs continuously is by design, at least for now.

The rationale behind was that a good moco cluster should consist of 3 or more
MySQL instances, so the chance of losing binlogs from all instances at the same
time was negligible.

[ymmt2005]

But I'm fine to change the design if anyone is willing to contribute.
In the end, the decision was also due to the time constraint.

[mhkarimi1383]

I'm into contribute since we need this thing, For this we should move the backup configurations from BackupPolicy into the MySQLCluster itself (if we want to contentiously upload using the agents in the node) and we will have a backup target (primary or prefer-standby) in the backup configurations

[ymmt2005]

I'm unsure why we need to move the backup configuration.
Anyway, please start with a design doc when you start contributing so that we'll be able to be on the same page.

[mhkarimi1383]

I will raise a PR for designdoc for this

[mhkarimi1383]

Before that I have some problems with moco itself (#782), I will start my design doc when they get solved