chore: handle referrer not registered in divvi integration

[kathaypacific]

Description

This PR ensures that the registration tx only contains protocolId's that the referrer is registered for. This prevents the prepared transaction from containing a protocolId that would cause the tx to revert (thereby blocking the rest of the transaction flow). A builder could be in this situation if they are developing before they are added to the registration contract.

Test plan

Setting the referrer id to a random string or adding a random protocol id to the app config does not affect the transaction flow.

Related issues

• Fixes RET-1318

Backwards compatibility

Y

Network scalability

If a new NetworkId and/or Network are added in the future, the changes in this PR will:

• Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

[jeanregisser]

Great! 🚀

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.08%. Comparing base (5fba34e) to head (1bfeebb).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #6496    +/-   ##
========================================
  Coverage   89.07%   89.08%            
========================================
  Files         732      732            
  Lines       31932    31944    +12     
  Branches     5833     6152   +319     
========================================
+ Hits        28445    28456    +11     
+ Misses       3440     3291   -149     
- Partials       47      197   +150     

Files with missing lines	Coverage Δ
src/divviProtocol/registerReferral.ts	95.55% <100.00%> (+0.68%)	⬆️

... and 67 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5fba34e...1bfeebb. Read the comment docs.