chore(dashmate)!: adjust consensus params and enable re-check

[shumkov]

Issue being fixed or feature implemented

We use default consensus timeouts for local and 0.24-based values for testnet. Re-check is not set so it's initializing as false. We have already more or less tested values and we need re-check to clean up mempool from unpaid invalid txs

What was done?

• set consensus timeouts
• adjust some other values
• enable re-check

How Has This Been Tested?

On devnet and locally by @lklimek

Breaking Changes

It will be a breaking change for any network since genesis params are changed

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
• I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone