Quickstart: run migrations after correcting the join-table migration (#8318)

The CMS quickstart bundled `bin/cake migrations migrate` in the same
copy-paste block as the bake commands. The baked articles_tags migration
needs a manual fix first (the composite primary key columns are generated
as auto-increment, which MySQL rejects), but that warning came after the
migrate step. Copying the whole block ran migrate before the fix and failed.

Move the migrate step to after the composite primary key warning so the
order is: bake, correct the migration, then migrate.

Author: dereuromark

docs/en/tutorials-and-examples/cms/database.md

@@ -66,9 +66,6 @@ bin/cake bake migration CreateUsers email:string password:string created modifie
 bin/cake bake migration CreateArticles user_id:integer title:string slug:string[191]:unique body:text published:boolean created modified
 bin/cake bake migration CreateTags title:string[191]:unique created modified
 bin/cake bake migration CreateArticlesTags article_id:integer:primary tag_id:integer:primary created modified
-
-# Run migrations to create tables
-bin/cake migrations migrate
 ```
 
 ```php [Migration Example]
@@ -120,6 +117,12 @@ $table->addColumn('tag_id', 'integer', [
 Remove the `autoIncrement` lines before running the migration to prevent foreign key problems.
 :::
 
+Once the `articles_tags` migration is corrected, run the migrations to create the tables:
+
+```bash
+bin/cake migrations migrate
+```
+
 #### Adding Seed Data
 
 Create seed files to populate initial data: