Smoke test takes too long to run

[hdevalence]

Describe the bug
A recent smoke test run took 16 minutes. Previously, we had it running in 4-6 minutes.

We should identify why it takes so much longer and find a way to cut the runtime.

[erwanor]

This is likely because we added submitting delegator voting / proposal submission to the smoke test in #2969

[conorsch]

We have the smoke tests set to run for an extra two minutes after the tests have completed, which we can easily shave off. More substantial gains can be found on the CometMock spike PR though: #2845 since we can dial the block time down even lower than the 500ms supported by CometBFT. Right now the delegate_and_undelegate test is failing, but I haven't even implemented block time travel yet, and the whole smoke test clocks in at <5m, which is a huge win. Will keep trying.

[hdevalence]

Is it desirable to use cometmock for the smoke test, though? Don't we want the smoke test to be testing the actual code we'll be running?

[hdevalence]

We can solve this problem by removing tests from the smoke test as our application-wide integration testing story matures (cc @cratelyn)

[cratelyn]

x-ref: #3588