[OTE-752] Add totalVolume and isWhitelistAffiliate to wallets table (backport #2166)

[mergify]

Changelist

[Describe or list the changes made in this PR]

Test Plan

[Describe how this PR was tested (if applicable)]

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

  • Introduced new properties totalVolume and isWhitelistAffiliate across various wallet-related functionalities to enhance wallet management and reporting capabilities.
  • Updated query configurations to allow filtering based on wallet affiliate status.

• Bug Fixes

  • Enhanced test cases to reflect the new wallet attributes, ensuring correct functionality and validation.

• Documentation

  • Updated documentation to include new properties in wallet-related interfaces and models, facilitating better understanding of wallet data structures.

• Chores

  • Systematic updates made across tests to align with new wallet object structures, improving overall test coverage and accuracy.

---

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

[mergify]

Cherry-pick of ecc5df6 has failed:

On branch mergify/bp/release/indexer/v6.x/pr-2166
Your branch is up to date with 'origin/release/indexer/v6.x'.

You are currently cherry-picking commit ecc5df61.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   indexer/packages/postgres/__tests__/stores/transfer-table.test.ts
	modified:   indexer/packages/postgres/__tests__/stores/wallet-table.test.ts
	new file:   indexer/packages/postgres/src/db/migrations/migration_files/20240827162119_add_wallets_total_volume_and_affiliates_whitelist.ts
	modified:   indexer/packages/postgres/src/models/wallet-model.ts
	modified:   indexer/packages/postgres/src/stores/wallet-table.ts
	modified:   indexer/packages/postgres/src/types/db-model-types.ts
	modified:   indexer/packages/postgres/src/types/wallet-types.ts
	modified:   indexer/services/comlink/__tests__/controllers/api/v4/transfers-controller.test.ts
	modified:   indexer/services/ender/__tests__/handlers/trading-rewards-handler.test.ts
	modified:   indexer/services/ender/__tests__/handlers/transfer-handler.test.ts
	modified:   indexer/services/ender/src/scripts/handlers/dydx_transfer_handler.sql

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   indexer/packages/postgres/__tests__/helpers/constants.ts
	both modified:   indexer/packages/postgres/src/types/query-types.ts

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[linear]

OTE-752 Update wallets table

[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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.