make sure domain is supported as sanity check in execute

[jakekidd]

Description

Seeing this error:

Which occurs in the catch block in packages/agents/lighthouse/src/lib/operations/cartographer.ts.

      } catch (error: any) {
        logger.error("Error Cartographer Binding", requestContext, methodContext, jsonifyError(error as NxtpError), {
          transaction,
        });
      }

It seems it's likely being thrown here, in packages/agents/lighthouse/src/lib/operations/relayer.ts.

  const destinationConnextAddress = config.chains[args.params.destinationDomain].deployments.connext;

I guess we're just not checking beforehand that a domain for a given transfer is supported. While all domains should be supported in theory, we should still catch this case especially for debugging our staging environment / broken configurations.

Type of change

Fire off an error, DomainNotSupported, if we don't have a given transfer's destination domain configured.

• Docs change / dependency upgrade
• Configuration / tooling changes
• Refactoring
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires changes in customer code