OTel kuttl test fix: add bad psql command to force an error and ensur…

[dsessler7]

…e there will be a postgres log to capture.

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)?

OTel kuttl test fails when backups turned off since no postgres logs are there to capture.

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

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

For the part of the test where the cluster has backups turned off, use psql to run a bad command that will force an error and ensure there will be a postgres log for OTel to capture.

Other Information: