fix order of enum values on MySQL 8

[Tantalon]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Fixes #3147.

On MySQL 5.7.12 enums values are retrieved in the correct order.
On MySQL 8.0.28 enums values are retrieved in this order: 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 20, 19, 18, 17...

This fix adds an order by so enums are explicitly retrieved in the correct order.

[github-actions]

Unit Test Results

  4 620 files  ±0    4 620 suites  ±0   37m 44s ⏱️ +17s
  4 617 tests ±0    4 398 ✔️ ±0     219 💤 ±0  0 ❌ ±0 
54 576 runs  ±0  49 552 ✔️ ±0  5 024 💤 ±0  0 ❌ ±0 

Results for commit e49d0c2. ± Comparison against base commit e742a88.

[nvoxland]

Code review and test results:

Things to be aware of:

• Code change makes sense
• There is not a great way currently to explicit test for enum ordering automatically, but existing tests would fail if the SQL is invalid

Things to worry about:

• Nothing

[XDelphiGrl]

• PR enforces chronological order of enums during column snapshot generation by including an ORDER BY clause to the generated SQL.
  • Fix addresses an issue specific to MySQL 8.
• No additional testing required.

APPROVED