Delete clone db once Postgres upgrade is confirmed to have no issue.

[zorn]

Today I executed a manual update of the database to Postgres 17. During that work a clone db was made to verify the upgrade would work without issue.

I've suspended the clone db (which should avoid it being billed) -- but we'll want to delete it once we know for sure the update went well.

flick_prod-upgrade-clone-459b