Move LibEVMVersion setting as last bullet point

Author: qdm12

libevm/tooling/release/README.md

@@ -15,10 +15,10 @@ In the following, we create a release candidate version `v1.13.14-0.2.0.rc.4`.
     The `myusername/release/v1.13.14-0.2.0.rc.4` branch will be used to add "release modifications" and will target the branch `release/v1.13.14-0.2.0.rc.4` in a pull request.
 1. Run the script `./cherrypick.sh` which cherry picks all Geth commits listed in [cherrypicks](cherrypicks). You may have to resolve conflicts.
 1. Modify [params/version.libevm.go](/params/version.libevm.go)
-    - Change the `LibEVMVersion` to the correct final version string (`version.libevm_test.go` will ensure that this is correctly formatted)
     - Change the `LibEVMReleaseType` to the correct release type, for example `ReleaseCandidate`
     - If planning a release candidate: set `libEVMReleaseCandidate` to the correct number; in this case `4`
     - If needed: change the `LibEVMVersionMajor`, `LibEVMVersionMinor` and `LibEVMVersionPatch` numbers
+    - Change the `LibEVMVersion` to the correct final version string (`version.libevm_test.go` will ensure that this is correctly formatted)
 1. Commit your modifications to [params/version.libevm.go](/params/version.libevm.go) with a commit title `chore: release v1.13.14-0.2.0.rc.4`.
 1. Push your modified branch to the remote `git push -u origin myusername/release/v1.13.14-0.2.0.rc.4`
 1. Open a pull request from your modified branch `myusername/release/v1.13.14-0.2.0.rc.4` and targeting `release/v1.13.14-0.2.0.rc.4`, for example with `https://github.com/ava-labs/libevm/compare/release/v1.13.14-0.2.0.rc.4...myusername/release/v1.13.14-0.2.0.rc.4?expand=1`. Set the title to "chore: release `v1.13.14-0.2.0.rc.4`"