Clarify migration docs can add not null in single MR for small tables

What does this MR do and why?

This previous documentation suggested you needed to split the changes across multiple releases but this is only necessary for large tables where you need a background migraiton for cleanup. Otherwise it should be safe to use a single merge request with 3 separate post_migrate migrations.

Discussed also in internal slack thread

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.