krakatoa: Fail when comet/app misconfigured

[technicallyty]

Actual need:

• Detect when Comet/App are not configured to work properly--i.e. we have krakatoa mempool in app and flood in comet or other configurations which we expect not to work.
• Fail startup when misconfigured.

Original context: im not sure if theres really a way to prevent this, but when mempool type in config.toml is set to flood, and you use the default app in evmd, you cannot send cosmos txs. it fails with sequence errors, as i assume checkTx has incremented sequence, and insert is checking this again.

[linear]

EVM-424

[mattac21]

IMO this is the expected behavior. Krakatoa is only really meant to be used without the comet mempool, if comet is calling into the app to do rechecks and managing txs itself, that will eliminate the point of the app side mempool. I think maybe we should just add in some validation here, where if you are using krakatoa (eventually we will make it configurable to turn the evm changes on and off), you must also have specified 'app' as your comet mempool.