test/e2e: mainnet phases test

[tzemanovic]

Describe your changes

Checklist before merging

• [ ] If this PR has some consensus breaking changes, I added the corresponding breaking:: labels
  • This will require 2 reviewers to approve the changes
• [ ] If this PR requires changes to the docs or specs, a corresponding PR is opened in the namada-docs repo
  • Relevant PR if applies:
• [ ] If this PR affects services such as namada-indexer or namada-masp-indexer, a corresponding PR is opened in that repo
  • Relevant PR if applies:

[codecov[bot]]

Codecov Report

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

Project coverage is 74.58%. Comparing base (cc531ec) to head (90a6493). Report is 16 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4013      +/-   ##
==========================================
- Coverage   74.58%   74.58%   -0.01%     
==========================================
  Files         341      341              
  Lines      107484   107484              
==========================================
- Hits        80167    80165       -2     
- Misses      27317    27319       +2     

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

[brentstone]

In general, I think we should be testing lots of actions in each phase to make sure what does and doesn't work as intended. For example, I wrote on the Namada forum some recommendations for users to test during Phase 3 and 4 of the dry-run:

• https://forum.namada.net/t/dry-run-phase-3-gov-proposal/1085/2?u=brentstone
• https://forum.namada.net/t/dry-run-phase-4-gov-proposal/1086/2?u=brentstone

[brentstone]

Hey @tzemanovic, what's the status here of this?

[tzemanovic]

Hey @tzemanovic, what's the status here of this?

I'm still trying to iron out some flakiness - sometimes it passes but sometimes there are pending packets left in hermes for a long time and it times out