Relayer: Recover XRPL originated token registration

[dzmitryhil]

Description

• Add contract client integration tests
• Add relayer (runners) integration test
• Add non-existing accounts error handing for the xrpl_tx_submitter

Reviewers checklist:

• Try to write more meaningful comments with clear actions to be taken.
• Nit-picking should be unblocking. Focus on core issues.

Authors checklist

• Provide a concise and meaningful description
• Review the code yourself first, before making the PR.
• Annotate your PR in places that require explanation.
• Think and try to split the PR to smaller PR if it is big.

---

This change is 

[miladz68]

Reviewed 6 of 6 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @wojtek-coreum and @ysv)

[ysv]

Reviewed 6 of 6 files at r1, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @dzmitryhil and @wojtek-coreum)

---

integration-tests/coreum/contract_client_test.go line 2244 at r1 (raw file):

	// try to recover the token with the unexpected current state
	_, err = contractClient.RecoverXRPLTokenRegistration(ctx, owner, issuer, currency)
	require.True(t, coreum.IsXRPLTokenNotInactiveError(err), err)

xrpl Token Not Inactive so is it active or not ?
I guess it is double negation done by mistake

either xrplTokenInactive or xrplTokenNotActive

---

integration-tests/coreum/contract_client_test.go line 2338 at r1 (raw file):

	require.Equal(t, coreum.TokenStateEnabled, registeredXRPLToken.State)
}

nit: this file is getting too big
Shall we split it into multiple by business logic or flows e.g: token registration, token send, contract administration ?

[dzmitryhil]

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @wojtek-coreum and @ysv)

---

integration-tests/coreum/contract_client_test.go line 2244 at r1 (raw file):

Previously, ysv (Yaroslav Savchuk) wrote…

xrpl Token Not Inactive so is it active or not ?
I guess it is double negation done by mistake

either xrplTokenInactive or xrplTokenNotActive

It is not Inactive. The only state when you can recover it is Inactive so when we try to recover with the state which is not Inactive we get that error.

---

integration-tests/coreum/contract_client_test.go line 2338 at r1 (raw file):

Previously, ysv (Yaroslav Savchuk) wrote…

nit: this file is getting too big
Shall we split it into multiple by business logic or flows e.g: token registration, token send, contract administration ?

We can think a bit later how to split it, the issue is that it is not so simple :-)

[ysv]

Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @wojtek-coreum)