Proactively update production referral rules config formatted for the next ENSNode v1.10.0 release

[lightwalker-eth]

In PRs such as #1874 and issues such as #1900 we are making breaking changes to the referral rules config schema.

We are currently running ENSNode v1.9.0 in production which is making use of the rules config published to https://ensawards.org/production-editions.json and managed in GitHub at https://github.com/namehash/ensawards/blob/main/ensawards.org/public/production-editions.json

We should be proactive in preparing an updated referral rules config for the upcoming ENSNode v1.10.0 release. There's already so many details to consider and configure with each new release. It's best not to leave this important detail to the last minute and instead to complete this update proactively as soon as we finish making the breaking schema changes that will later go live in the v1.10.0 release.

At the same time, we need to avoid making any changes to this production-editions.json file for now as it's being used live in production by ENSNode v1.9.0.

Therefore, instead of modifying the existing production-editions.json file, please create an all new production-editions-v1.10.0.json file that has all the configuration needed to be ready for when we deploy ENSNode v1.10.0.

[coderabbitai]

🔗 Related PRs

#1712 - rev-share-limit Referral Program Disqualification [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!