refactor: clean up chain error message handling

[p0mvn]

Context

To format chain error message, we do regex parsing:

osmosis-frontend/packages/web/components/alert/prettify.ts

Lines 6 to 19 in a2d830e

	const regexLegacySignatureVerificationFailed =
	/^signature verification failed; please verify account number \(\d*\), sequence \((\d*)\) and chain-id \(.*\): unauthorized/;
	const regexSignatureVerificationFailed =
	/^account sequence mismatch, expected (\d*), got (\d*): incorrect account sequence/;
	const regexFailedToExecuteMessageAt =
	/^failed to execute message; message index: (\d+): (.+)/;
	const regexCoinsOrDenoms = /(\d*)([a-zA-Z][a-zA-Z0-9/]{2,127})(,*)/g;
	const regexSplitAmountAndDenomOfCoin = /(\d+)([a-zA-Z][a-zA-Z0-9/]{2,127})/;
	const regexInvalidClPositionAmounts =
	/failed to execute message; message index: (\d+): slippage bound: insufficient amount of token (\d+) created. Actual: \((\d+)\). Minimum estimated: \((\d+)\)/;
	const regexFailedSwapSlippage =
	/failed to execute message; message index: \d+: (.*?) token is lesser than min amount: calculated amount is lesser than min amount: invalid request/;

A cleaner approach would be to check SDK error codes like we do here:

osmosis-frontend/packages/web/components/alert/tx-event-toast.ts

Lines 79 to 81 in a2d830e

	if (tx.code === txTimeoutHeightReachedErrorCode) {
	return "errors.txTimedOutError";
	}

An example of an error code: https://github.com/cosmos/cosmos-sdk/blob/8f6a94cd1f9f1c6bf1ad83a751da86270db92e02/types/errors/errors.go#L129

We should refactor our error handling and formatting to be dependent on error codes as opposed to regex matching

Acceptance Criteria

• Cleaned up errors
• Error codes used
• All tested
• No error message is broken by the refactor