Remove default partition value from CI tables

What does this MR do and why?

!126001 (diffs) removed the database default values for a bunch of columns(we used the default to backfill the values, the app now provides the values) and some of the tables had high autovacuum(wraparound prevention mode) time which means that the migrations had a change of failing on .com, blocking the deployments. Because of this problem, those tables were guarded by a vacuum check. Now that everything is successfully executed in production, we can release them to self-managed instaces.

TLDR: The migrations here are no-ops for .com and can be skipped.

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.

Related to #377822 (closed)