Speed up KUTTL tests by dropping backups

[benjaminjb]

Checklist:

• Have you added an explanation of what your changes do and why you'd like them to be included?
• Have you updated or added documentation for the change, as applicable?
• Have you tested your changes on all related environments with successful results, as applicable?
  • Have you added automated tests?

Type of Changes:

• New feature
• Bug fix
• Documentation
• Testing enhancement
• Other

What is the current behavior (link to any open issues here)?

What is the new behavior (if this is a feature change)?

• Breaking change (fix or feature that would cause existing functionality to change)

Other Information:
Issues: [PGO-1572]

[tony-landreth]

Does the test run slower when backups are off and replicas > 1?

[benjaminjb]

Good question, I see four tests that have replicas and need them, so I'm testing them out:

• replica-read
  • w/ backups: ~28s
  • w/o backups:~25s
• scaledown
  • w/ backups: ~2m
  • w/o backups:~3m
• switchover
  • w/ backups: ~37s
  • w/o backups:~34s

So adding backups back to Scaledown files for now and testing.

[benjaminjb]

Optional backups PR with new KUTTL test:

KUTTL tests trimmed to avoid backups

And after a few tweaks to the tests: