feat: add router for contribution fees

[0xble]

Implements a crowdfund router that allows contributions to include a flat fee before being passed on to the crowdfund

[height]

This pull request has been linked to 2 tasks:

• T-3245 Implement standalone wrapper with fee as function input (unlink task)
• T-3246 Implement standalone wrapper with fee in storage (unlink task)

💡Tip: Add "Close T-3245" to the pull request title or description, to a commit message, or in a comment to mark this task as "Done" when the pull request is merged.

[codecov-commenter]

Codecov Report

Patch coverage: 79.06% and project coverage change: +0.35% 🎉

Comparison is base (0a9fc2f) 60.61% compared to head (bcfd966) 60.96%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #282      +/-   ##
==========================================
+ Coverage   60.61%   60.96%   +0.35%     
==========================================
  Files          62       63       +1     
  Lines        2458     2475      +17     
  Branches      573      573              
==========================================
+ Hits         1490     1509      +19     
- Misses        772      775       +3     
+ Partials      196      191       -5     

Files Changed	Coverage Δ
contracts/crowdfund/Crowdfund.sol	52.57% <0.00%> (-0.92%)	⬇️
contracts/crowdfund/ETHCrowdfundBase.sol	80.37% <ø> (ø)
contracts/gatekeepers/AllowListGateKeeper.sol	77.77% <0.00%> (-22.23%)	⬇️
contracts/gatekeepers/TokenGateKeeper.sol	88.88% <50.00%> (-11.12%)	⬇️
contracts/crowdfund/ContributionRouter.sol	100.00% <100.00%> (ø)
contracts/crowdfund/InitialETHCrowdfund.sol	86.56% <100.00%> (+4.87%)	⬆️
contracts/crowdfund/ReraiseETHCrowdfund.sol	78.63% <100.00%> (+2.59%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[arr00]

Link T-3246

[arr00]

We shouldn't use globals here for who can call the claim fees fn. Let's pass an owner on construction and have it be more generic wording.

[arr00]

For simplicity, we don't actually need to know which type of crowdfund the user is contributing in this contract. It can just be a low level eth call with the given calldata to the given crowdfund. That may be a better approach.

[0xble]

For simplicity, we don't actually need to know which type of crowdfund the user is contributing in this contract. It can just be a low level eth call with the given calldata to the given crowdfund. That may be a better approach.

It's more flexible. Would save us from having to redeploy if we were to add new crowdfund types. And could be adapted to add an optional to any function call, really. I say we go for it.

[arr00]

Do we care to be able to switch the owner of the wrapper? I assume its fine like this.

[0xble]

Do we care to be able to switch the owner of the wrapper? I assume its fine like this.

Since owner is going to be the DAO's multisig, it's unlikely to change. Worse case and it does change, can always deploy a new one with an updated owner and switch over to that.

[arr00]

Let's add the audit then LGTM!