Cherrypick 33655 fix into 4.75.0

[JordanMontgomery]

Related issue: Resolves #33562

Detects and if possible fixes migrations which were misnumbered in the released 4.73.2 Linux binary(it was based on the commit before the renumbering commit was added). This does not affect the released 4.73.2 docker images and this code does nothing on these since the migrations will not be detected

We specifically look for the 3 most recent migrations being the mis-numbered 4.73.2 and 4.73.1 migrations in the expected order. If neither of the mis-numbered migrations are found, nothing is done. Likewise if the order is not right or the order is not exactly right(e.g. if intervening migrations, for instance from 4.74.0 have been applied) we do not apply the fix. Finally, the fix is only ever applied in the existing migration path and fleet will never try to apply the fleet automatically by just running the fleet server(though it will detect the condition and complain)

Checklist for submitter

If some of the following don't apply, delete the relevant line.

• Changes file added for user-visible changes in changes/, orbit/changes/ or ee/fleetd-chrome/changes.
  See Changes
  files for more information.

• Input data is properly validated, SELECT * is avoided, SQL injection is prevented (using placeholders for values in statements)

• If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes

Testing

• Added/updated automated tests

• Where appropriate, automated tests simulate multiple hosts and test for host
  isolation (updates to one hosts's records do not affect another)

• QA'd all new/changed functionality manually

For unreleased bug fixes in a release candidate, one of:

• Confirmed that the fix is not expected to adversely impact load test results
• Alerted the release DRI if additional load testing is needed

Database migrations

• Checked table schema to confirm autoupdate
• Checked schema for all modified table for columns that will auto-update timestamps during migration.
• Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects.
• Ensured the correct collation is explicitly set for character columns (COLLATE utf8mb4_unicode_ci).

[codecov]

Codecov Report

❌ Patch coverage is 29.46429% with 79 lines in your changes missing coverage. Please review.
⚠️ Please upload report for BASE (rc-minor-fleet-v4.75.0@0fd27e2). Learn more about missing BASE report.

Files with missing lines	Patch %	Lines
cmd/fleet/prepare.go	0.00%	35 Missing ⚠️
cmd/fleet/serve.go	0.00%	24 Missing ⚠️
server/datastore/mysql/mysql.go	64.70%	12 Missing and 6 partials ⚠️
cmd/fleet/vuln_process.go	0.00%	2 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                    @@
##             rc-minor-fleet-v4.75.0   #33689   +/-   ##
=========================================================
  Coverage                          ?   64.04%           
=========================================================
  Files                             ?     2067           
  Lines                             ?   207169           
  Branches                          ?     6720           
=========================================================
  Hits                              ?   132686           
  Misses                            ?    64047           
  Partials                          ?    10436           

Flag	Coverage Δ
backend	65.15% <29.46%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.