A PR recently landed to allow primary key changes to handle when indexes are being rebuilt. However, I'm worried about different cases (such as column additions) where the setup for the primary key change needs to coordinate with other in progress mutations.

We should first audit primary key changes and see interactions with other concurrent schema changes. If the scope of changes seems too large, disable primary key changes while other schema changes are executing.