Database migrations typically refer to schema/ddl changes to an application along side deployment of a new version.

Everything I've ever heard and read has told me that containers aren't a good for for this type of long-term service that gets refreshed infrequently.

That was a safe rule of thumb 5 years ago. Since then support for scheduling a persistent volume to be available along side your long running container has become a bog standard and boring feature.