Reorder SQL migrations to fix some upgrade issues

[hbeatty]

What does this PR (Pull Request) do?

This moves some SQL migrations past the last one in 5.0.x that were not in the 4.1.x and 5.0.x branch.

• This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

• Traffic Ops

What is the best way to verify this PR?

Do a DB upgrade from 5.0.0 to 5.1.0

If this is a bug fix, what versions of Traffic Control are affected?

• 5.0.0
• 5.1.0

The following criteria are ALL met by this PR

• This PR includes tests OR I have explained why tests are unnecessary
• This PR includes documentation OR I have explained why documentation is unnecessary
• This PR includes an update to CHANGELOG.md OR such an update is not necessary
• This PR includes any and all required license headers
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[rawlinp]

Ok, once this is merged it can be backported to 5.1.x, so we don't need #5528.

[ocket8888]

Yeah, I can do that for you. No need of a separate PR

[hbeatty]

Just curious what the difference is?

[rawlinp]

By cherrypicking, we include the original commit hash from master by using the -x option. It also helps ensure that the master version and the 5.1.x version are actually the same changes (in case we request changes here which would cause it to diverge from the 5.1.x PR that was opened simultaneously).

[rawlinp]

LGTM, DB upgrades from 2020110200000000_add_service_category_deleted.sql (first migration script in 5.0) to the latest and downgrades back successfully.