BCF 2440 remove chainsets from core

[krehermann]

The key points to this are:

BCF-2317 hid all the chainset from public API with the core node
BCF-2564 updated all the chain-specific repos to accept a chain instead of a chainset

The main thrust of this change is

• plumbs the new signatures implemented in BCF-2564, which removes the internal dependency on chainsets
• removes the chainset implementations

However, there are some contortions needed to accomplish this while maintain compatibility with the existing loop.Relayer interface.

We have to maintain funcs that had been on the ChainSet implementations:

	ChainStatus(ctx context.Context, id string) (ChainStatus, error)
	ChainStatuses(ctx context.Context, offset, limit int) (chains []ChainStatus, count int, err error)

	NodeStatuses(ctx context.Context, offset, limit int, chainIDs ...string) (nodes []NodeStatus, count int, err error)

	SendTx(ctx context.Context, chainID, from, to string, amount *big.Int, balanceCheck bool) error

We do this with foresight about BCF-2441, which is drafted here: smartcontractkit/chainlink-common#158, and proposes to replace these interface funcs with

  GetChainStatus(ctx context.Context) (ChainStatus, error)
	ListNodeStatuses(ctx context.Context, page_size int32, page_token string) (stats []NodeStatus, next_page_token string, err error)
	// choose different name than SendTx to avoid collison during refactor. we can revert to SendTx if needed after core is rid of conflicting funcs
	Transact(ctx context.Context, from, to string, amount *big.Int, balanceCheck bool) error

Therefore, there are two aspects to playing nicely with the loop.Relayer interface. First is maintaining the exist required funcs in the interface. Second is preemptively adding support for the new interface definition that is drafted above.

In order to ensure an easy transition when BFC-2441 lands, we implement the new funcs and in turn implement the old funcs in terms of them. This is quite nice because we can use all of the existing tests to ensure our new interface funcs are correct. For non-evm chains this can be done in one place, in the RelayExt and RelayAdapter: We define the existing interface funcs on this struct and implement them in terms of the chain that they receive during construction.

EVM is a little more complex, which is to be excepted.

Once BCF-2441 is merged, and we will update this repo to remove all the deleted funcs and expose the already-implemented funcs in there place. There are many TODOs marking the places that can and will be simplified.

[jmank88]

nit/ The branch is prefixed as BCF-2441- - will this confuse Jira?

[cl-sonarqube-production]

SonarQube Quality Gate

69.1% Coverage on New Code (is less than 80%)
15.89% Duplicated Lines (%) on New Code (is greater than 3%)

See analysis details on SonarQube