Clarify when migrations should be squashed

What does this MR do and why?

Clarify when migrations should be squashed

Migrations should always be squashed after a required stop. Not just when a stop is database related. Update docs to reflect this.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

added Category:Database docs-only groupdatabase maintenancerelease sectionenablement typemaintenance labels

assigned to @alexives

@jon_jenkins would you mind taking a look at this?

requested review from @jon_jenkins

added devopsdata stores sectioncore platform labels and removed sectionenablement label

added development guidelines docsimprovement documentation maintenancerefactor labels and removed maintenancerelease label

	1 Warning
	This merge request does not refer to an existing milestone.

	1 Message
	This MR contains docs in the /doc/development directory, but any Maintainer (other than the author) can merge. You do not need tech writer review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

approved this merge request

started a merge train

removed this merge request from the merge train because the pipeline did not succeed. Learn more.

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit 8d726b83

added workflowstaging-canary label

changed milestone to %17.4

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-production label and removed workflowproduction label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added groupdatabase frameworks label and removed groupdatabase [DEPRECATED] label