Add a vmbackup option to skip tagging directive

Is your feature request related to a problem? Please describe

Some S3 solutions do not adhere to the S3 API specification, resulting in an HTTP 400 error when calling CopyObject with tagging directives. See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/10922#issuecomment-4396250130 for more information.

Describe the solution you'd like

Add a flag that allows the user to skip the tagging directive

Describe alternatives you've considered

Downgrading vmbackup to 1.136.1 works, but this complicates the manifests and doesn't include recent fixes

Additional information

This option should be left at user discretion, when they are informed about potential downsides of removing this rule but don't have an option to use a different S3 storage