feat: create token bridge

[spsjvc]

todos:

• don't hardcode gas limit for parent chain tx
• add padding to retryable fees
• custom gas token support
  • create util for approving the retryable fees to the token bridge creator
  • add integration test for custom gas token
• create getTokenBridgeContracts function on CreateTokenBridgeTransactionReceipt that parses logs and returns contracts
  • try using the registry
  • add assertions related to getTokenBridgeContracts to existing token bridge integration tests
• clean up abi
• add example for creating a token bridge

[TucksonDev]

Should we use the inbox address for this, or the rollup address?

[spsjvc]

It's fine if we use rollup

[TucksonDev]

I'm leaning towards not changing this now. In getTokenBridgeContracts we get the inbox from the OrbitTokenBridgeCreated event, and then we need to get the bridge address, and finally the rollup address.
Then, here, in createTokenBridgeFetchTokenBridgeContracts, we would need to get the inbox address from the rollup anyway.

This back and forth is what doesn't convince me for now. If we ever see the need to use rollup here in the future (in other use cases), it might make sense to refactor it then.

[spsjvc]

It's fine if we use rollup

[TucksonDev]

Added checks for successful retryables execution

[spsjvc]

I think we can simplify this a bit and just have a pure function for percent increase:

Suggested change

	export function applyGasOverrides({
	gasOverrides,
	estimatedGas,
	defaultGas,
	}: {
	gasOverrides: GasOverrideOptions;
	estimatedGas?: bigint;
	defaultGas: bigint;
	}) {
	const baseEstimatedGas = gasOverrides.base ?? estimatedGas ?? defaultGas;
	return gasOverrides.percentIncrease
	? baseEstimatedGas + (baseEstimatedGas * gasOverrides.percentIncrease) / 100n
	: baseEstimatedGas;
	}
	export function applyPercentIncrease({
	base,
	percentIncrease = 0
	}: {
	base: bigint;
	percentIncrease?: bigint
	}) {
	return base + (base * percentIncrease) / 100n
	}

[spsjvc]

I think we can make this a bit simpler (combined with the change from the other comment):

Suggested change

	// potential gas overrides (gas limit)
	if (gasOverrides && gasOverrides.gasLimit) {
	request.gas = applyGasOverrides({
	gasOverrides: gasOverrides.gasLimit,
	estimatedGas: request.gas,
	defaultGas: createTokenBridgeDefaultGasLimit,
	});
	}
	// potential gas overrides (gas limit)
	if (gasOverrides && gasOverrides.gasLimit) {
	request.gas = applyPercentIncrease({
	base: gasOverrides.gasLimit.base ?? request.gas,
	percentIncrease: gasOverrides.gasLimit.percentIncrease,
	});
	}

Don't think we really need to have defaults in here, it's good enough to expose as constants so the consumer can do:

createTokenBridge({
  ...,
  gasOverrides: {
    gasLimit: {
      base: createTokenBridgeDefaultGasLimit
    }
  }
})