Explicitly lock tables for partitioning

What does this MR do and why?

related to #378644 (closed) and #373239 (closed)

It changes the previous migration into a no-op and enqueues a new one where we try to lock the tables in the order in which the application uses them. This should allow the lock to be acquired without causing deadlocks.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.