refactor: use docker healthcheck for localnet e2e

[gartnera]

Description

Use a docker health check rather than sleeping in e2e to wait for e2e start. Also reduce keygen height.

The keygen height parameters are very sensitive, the following combinations seem to result in random test failures:

• 20 25
• 20 30
• 25 30

I have selected parameters which appear to be stable, but I will need a few CI runs to know for sure.

Reduced CI time by 30-60 seconds, but is mostly to make local development faster.

Update: need to accelerate preparams generation a bit. Also cache it on a docker volume to avoid pointless recomputation when running locally.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

• Tested CCTX in localnet
• Tested in development environment
• Go unit tests
• Go integration tests
• Tested via GitHub Actions

Checklist:

• I have added unit tests that prove my fix feature works

[lumtis]

LGTM if CI passes

[gartnera]

LGTM if CI passes

I'm having a hard time telling if e2e is just generally unstable or if this change is causing more instability

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 68.72%. Comparing base (5e3c3ba) to head (bb9309d).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #2353      +/-   ##
===========================================
- Coverage    68.72%   68.72%   -0.01%     
===========================================
  Files          302      302              
  Lines        19168    19169       +1     
===========================================
  Hits         13174    13174              
- Misses        5347     5348       +1     
  Partials       647      647              

Files	Coverage Δ
zetaclient/config/config.go	0.00% <0.00%> (ø)

[julianrubino]

LGTM