chore: Replacing v5.0.0 upgrade handler with v5.0.2

[spoo-bar]

• Replace v5.0.0 upgrade handler with v5.0.2
• Update the interchaintests workflows to run on release branches too
• Updating interchaintest workflow to use hardcoded previous version as v4.0.2. By default, it takes the last released tag. Which in this case is v5. we want to test upgrade from v4.0.2

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (releases/5.0.x@75443a6). Click here to learn what that means.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## releases/5.0.x #499 +/- ## ================================================= Coverage ? 69.38% ================================================= Files ? 70 Lines ? 4139 Branches ? 0 ================================================= Hits ? 2872 Misses ? 1163 Partials ? 104 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[spoo-bar]

Please confirm: Using v4.0.2 hard coded as initial version to ensure clean upgrade path to v5.0.2...

The hardcoded values are just for the tests as the mainnet will go from v4.0.2 to v5.0.2 which we would like to simulate. The variable used before would return v5.0.1 as that was the last tagged release and test the upgrade from v5.0.1 to v5.0.2 which is invalid.