feat: add allowance module for Citrea mainnet and testnet

[Emosaddd]

testnet

deploying "AllowanceModule" (tx: 0xcffb87cda2be98e4757f0e0c07d2b6de4e2fb36e8303fd03dd7af52eea7da6e4)...: deployed at 0xAA46724893dedD72658219405185Fb0Fc91e091C with 3273619 gas

mainnet

deploying "AllowanceModule" (tx: 0x6ffb7920c5a4aac78e8a5eab83301fb54075a4717a3e38d7b0ae16e94f93d4f7)...: deployed at 0xAA46724893dedD72658219405185Fb0Fc91e091C with 3273619 gas

[Emosaddd]

Hello @dasanra
could we proceed here?

[Zalens]

Hey @Emosaddd, this PR has a merge conflict with main (caused by #109 which recently merged and touched the same area of allowance-module.json).

Could you rebase onto main? The conflict is straightforward — just the networkAddresses section in src/assets/allowance-module/v0.1.1/allowance-module.json.

[Emosaddd]

Hey @Emosaddd, this PR has a merge conflict with main (caused by #109 which recently merged and touched the same area of allowance-module.json).

Could you rebase onto main? The conflict is straightforward — just the networkAddresses section in src/assets/allowance-module/v0.1.1/allowance-module.json.

Hey @Zalens
done

[Zalens]

AllowanceModule verified on-chain for Citrea mainnet (4114) and testnet (5115). Address matches canonical. Also fixes pre-existing sort order issue for chain 3637. Numeric sorting correct after change.

[Zalens]

This PR has merge conflicts after other allowance module PRs were merged. Could you rebase on main? Everything else is approved — on-chain verification passed and conventions look good.