adds db-cleaner deploy files for db operation needs

[tonytheleg]

PR Template:

Describe your changes

• adds extra deployment files that can be leverage for one off aggressive DB operations when needed
• initial use case is to drop key tables to allow the migrate command to recreate them with new data types (See RHCLOUD-35930: converts uint64 id's to uuidV7 #220)
• These would need to be targeted by saas file before they run so no danger in adding them

Ticket reference (if applicable)

Fixes #

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[tylercreller]

LGTM