feat: kolibri integration

[0xSulpiride]

Description

• feat: kolibri integration
• feat: config param for optional kolibri auth key

Tested on Polygon (BEV endpoint: https://bev-relay.kolibr.io)
https://polygonscan.com/tx/0x25c6a0423158ba73e4d891b09c8724773b8fef307ff4bf3c7d620a94974bd267
https://polygonscan.com/tx/0xfcce72092e9c4ddef8bc9100e6401c7d4c694edf672bc6943e5293692445c15b
https://polygonscan.com/tx/0x5fc1f93cdcc233f8245d891072b7de9374f3790d32157bbc2fb001558224850e

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (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 not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Other (please describe):

Further comments (optional)

[ch4r10t33r]

LGTM. Do you want to amend merkle to sendBundle as well (In the same same PR)?

[0xSulpiride]

Do you want to amend merkle to sendBundle as well (In the same same PR)?

because sendBundle is from a different API I think I'll need to rework Merkle integration completely, so I think it should be a separate PR

[ch4r10t33r]

Do you want to amend merkle to sendBundle as well (In the same same PR)?

because sendBundle is from a different API I think I'll need to rework Merkle integration completely, so I think it should be a separate PR

Sounds good to me.