Dont attribute new revenue if user exceeds 30d max volume and deprecate AffiliateWhitelist (backport #3109)

[jusbar23]

Changelist

• Update protocol to use overrides instead of whitelist
• Don't attribute new revenue if user exceeds 30d max revenue
• Add overrides to automatically set tier to max

Test Plan

• Test cases

Side Effects:

• Affilliate whitelist will no longer be recognized, only affiliate overrides

Author/Reviewer Checklist

• If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
• If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
• If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
• If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
• If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
• Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

• New Features

  • Stats now record per-fill affiliate fees and per-user affiliate revenue; stats expiration hooks enforce a 30-day rolling window and adjust attributed volumes.
  • Affiliate overrides (per-address) replace the previous whitelist behavior.
  • New API to retrieve user-specific stats.

• Changes

  • Top affiliate tier taker fee share increased to 25% (from 20%).
  • Rev-share and match processing now propagate affiliate revenue/override data; attribution caps applied and updated on expiration.

• Documentation

  • Clarified that global and user stats represent a 30-day rolling window.

• Chores

  • Affiliate CLI reads client config and uses renamed parameters.

---

This is an automatic backport of pull request #3109 done by [Mergify](https://mergify.com).

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch justin/release-don_attribute

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}