[8.x] Move primary after collate

[Synchro]

This simply changes the clause order in the MySQL grammar, and appears to fix #37811 in a similar way to the fix that resulted in the 8.48.1 release (which failed for me). I don't know what the definitive order of clauses should be, but this change fixes the issue I found.

[driesvints]

Ping @khalilst

[khalilst]

@driesvints , @Synchro I have checked the problem and it was related to charset ordering and not collate.
Line 18 in the commit could be like this:

'Unsigned', 'Charset', 'Primary', 'Collate', 'VirtualAs', 'StoredAs', 'Nullable',

However the current ordering in this PR has no problem, but putting the Primary after Collate is NOT necessary.
I will create another test for this fix.

[driesvints]

@khalilst we got another issue about the original PR: #37820

I'm sending in a PR to revert all of this.

[khalilst]

@driesvints Just give me an hour to fix this: #37820 .

[Synchro]

FWIW I've updated this PR to move it to after charset instead of collate.

[khalilst]

@khalilst we got another issue about the original PR: c

I'm sending in a PR to revert all of this.

@driesvints
I have checked issue #37820 and it was working without any problem.
Probably, it was a wrong bug report or there is something missing there.

[driesvints]

We're gonna revert all of this.

[khalilst]

@driesvints I think these bugs are very tiny ones. Just need more test cases to prevent a similar situation.

@taylorotwell Please consider this issue #33238

[taylorotwell]

@khalilst we will give this a bit longer but we don't particularly care about DigitalOcean's problems. They aren't ours to fix. Complain to them.

[Synchro]

Thanks for merging

[khalilst]

@taylorotwell Thanks and I do agree.
Please consider it will result in a single query and faster execution. however, it is very small.