Description

#24369 reverted the commit that introduced migration 115. Instead of deleting 115, it modified it. The problem with this is:

• the migration now does nothing
• the migration can't just be updated in the future, because after it runs once for a user, it will never be run again

What we need to do is delete migration 115 and then rename the subsequent migrations to one number lower (and update their contents to reflect these new migration numbers. Then, when the reverted changes are restored, the migration can be re-added as the new highest numbered migration.

This PR makes the changes needed to delete migration 115 over multiple commits, for ease of review. Reviewing this PR is really easy if you review commit by commit (but Github can't easily display the simplicity of the changes when they are all together). Below I have briefly described each commit and included a screenshot of what you will see if you click the link to look at that commit directly

e7d4cb5 Deletes the existing migration 115 files

8d78df3 Renames the existing migration 116 files to migration 115 files

3023d17 Renames the existing migration 117 files to migration 116 files

23f121b Renames the existing migration 118 files to migration 117 files

f6cbb92 Renames the existing migration 119 files to migration 118 files

f40afd7 Modifies the renamed files from the previous commits, so that any number within those files in the range 115-119 is replaced by the number one below.

088ecd5 Just deletes 1 line from app/scripts/migrations/index.js

Manual testing steps

1. Create a local build on the master branch, install and onboard
2. Create a build on this branch, install
3. In the background console, you should see logs that show migrations 115 to 118 running successfully

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.