Remove account storage format V1

[turbolent]

Follow-up to #3584

Description

Now that all production networks were migrated to storage format V2, we can remove format V1.

However, to avoid having to deploy this change in a HCU / avoid making this change produce a different execution result, we need to keep the existing logic / reads to determine the storage format.

If an account in format V1 is detected, abort execution with a new error.

---

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[github-actions]

Cadence Benchstat comparison

This branch with compared with the base branch onflow:master commit 61b9ab6
The command for i in {1..N}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done was used.
Bench tests were run a total of 7 times on each branch.

Collapsed results for better readability

[turbolent]

Unfortunately we won't be able to remove the read of the domain register / V1 reads here, because that will produce a different execution result, i.e. require a HCU.

[fxamacker]

Nice! Thanks for removing code related to storage format V1.

Since there are still register reads related to storage format V1, I opened an issue #3815 as a reminder for next HCU.