ens-referrals: Migrate utility functions from ENSAwards to `ens-referrals`

[Y3drk]

Goal

Any logic or data types in ENSAwards that might in theory be useful to anyone else building an app related to ENS Referrals should be moved into the ens-referrals package.

Functions to migrate

NOTE: more functions might be added in the future

• isReferrerDisqualified & isReferrerWarned
• filterOutUnrecognizedEditions
• Function to calculate the additional revenue contribution required for classification or how many more referral years are required for classification.
  • Fairly low priority, as the formulas are quite easy. Could be inspired by code fragments like this or this

Why

• Requested by @lightwalker-eth here
• Will help us (and our users) in the future, especially if we wanted to build some other app on top of ensanalytics/ens-referrals

[coderabbitai]

🔗 Related PRs

#1712 - rev-share-limit Referral Program Disqualification [merged]
#1938 - Using NormalizedAddress in referral program logic [merged]
#1943 - Introducing admin actions to handle disqualifications and warnings [merged]
#1973 - Refining the Leaderboard Calculation [merged]
#1986 - Prevent overlapping referral program editions [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!