test: Remove badNonce retries and increase nonce maxConnectionAge

[beautifulentropy]

The nonce service's maxConnectionAge (30s) periodically results in a GOAWAY being sent to the WFE's gRPC connections, causing affected SubConns to briefly leave READY state while reconnecting. Due to jitter on maxConnectionAge, the getNonceService and redeemNonceService connections to the same backend can GOAWAY at slightly different times, creating a window where the WFE can still issue nonces from a backend it can no longer redeem against. The chisel2.py retry logic was added to paper over this, but retries mask real failures.

Note: no corresponding change is made/possible in the Go integration tests because badNonce retries are handled internally by github.com/eggsampler/acme.

Since integration test runs complete well within 30 minutes, increasing maxConnectionAge to 30m ensures nonce connections are never cycled during a CI run, which should eliminate the flake.

A follow-up PR will address the underlying issue.

Part of #8662

[jsha]

Looks good in general but there is some weirdness with the diff showing changes from other PRs that were already merged.

[github-actions]

@beautifulentropy, this PR appears to contain configuration and/or SQL schema changes. Please ensure that a corresponding deployment ticket has been filed with the new values.

[beautifulentropy]

Looks good in general but there is some weirdness with the diff showing changes from other PRs that were already merged.

All fixed, apologies for the force-push.

[beautifulentropy]

@beautifulentropy, this PR appears to contain configuration and/or SQL schema changes. Please ensure that a corresponding deployment ticket has been filed with the new values.

No need, we don't plan to make a corresponding change to this value in staging/production.