Clean up old data migrations from Foreman < 2.0
Many old data migrations can be cleaned up, specifically migrations that were used to modify data structures during upgrades.
These migration are not needed on new installs, and any upgrades will have executed them by now.
We do not support upgrading multiple versions at once, and considering Foreman 3.1 will soon be released it should be safe to clean up any such migrations from before 2.0.
Fixes #33909 - Drop data migrations before Foreman 2.0
All data migrations only modify data on upgrades. On new installs they
are not required. Since we do not generally support upgrading multiple
releases, we can clean up old data migrations. This commit cleans up all
the data migrations that were present before Foreman 2.0.
Refs #33909 - Delete empty migrations
New installs will not run these empty migrations, and old installs will
only list that they have been executed when checking the `rake
db:migrate:status` with no file, which is harmless.
Refs #33909 - Remove useless User lookup
There is no need to lookup the admin user and use it to update the
http proxy fields.
Refs #33909 - Reset User column information
While migrations shouldn't rely on any users existing in the DB, there
are some that currently do. If they try to use User.find_by_lower_login
they will currently error out since the method won't be defined yet.