Prevent ZETA withdraw at the protocol level if ZETA not enabled

[lumtis]

For new added supported networks, we don't enabled ZETA withdraws.

However, a CCTX can still be initiated by interacting with the connector. This create the CCTX that gets reverted or aborted/
This will lead to:

• UX confusion as there are no information feature is disabled
• fee payment for the CCTX before reverting
• worst case scenario: aborted because message passing was used an no hook for the revert

We need to prevent at the protocol level from initiating a CCTX if ZETA is not support and gives a message that it is not supported.

One solution can be to use the ChainParams: ZetaTokenAddress or ConnectorAddress not set mean it is disabled.

[lumtis]

Adding for August release as it can be part of the smart contract environment migration. Need to assess complexity.

[lumtis]

ZETA has been disabled in the gateway contract