[Task] Update upgrade E2E test to run a series of upgrades rather than a single version

### What is this about?

This ticket is meant to update the E2E upgrade test to include more legacy versions and have the automation upgrade through multiple versions. The issue below could have been detected if there was an upgrade test from 7 versions prior. [Here](https://mixpanel.com/s/E9WLX) is Mixpanel data to support upgrade version decision.

Related Issue: https://github.com/MetaMask/metamask-mobile/issues/12207
Fix: https://github.com/MetaMask/metamask-mobile/pull/12219

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

https://docs.google.com/document/d/1hOPiaJBT64ydkRSZ9twY0kT6DUJ36lcE6RLbtpbWQ-w/edit?tab=t.0#bookmark=id.9c1gz7am7yv

Review the existing E2E upgrade test and the related issue 12207 and fix PR 12219. Done means the test covers additional legacy versions and upgrades through a sequence rather than a single version.

Written by the indexing model from the issue text.