[PAY-3315][PAY-3316][PAY-3323] Staking bridge

[sddioulde]

Description

Left to do in this PR:

• callers of get_legacy_purchase_gate should pass in the include_network_cut conditionally
• payment indexing should validate staking bridge usdc payout wallet if network cut is included in transaction
• update staking_bridge_usdc_payout_wallet in DN config
• from libs folder run npm run gen:dev to update sdk types
• test end-to-end flow e.g. make track purchase from client

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide repro instructions & any configuration.

[gitguardian]

⚠️ GitGuardian has uncovered 9 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11648676	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/discovery-one.env	View secret
11648676	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/discovery-one.docker.env	View secret
11648678	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-three.docker.env	View secret
11648678	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-three.env	View secret
11648679	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-two.docker.env	View secret
11648679	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-two.env	View secret
11648680	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-one.docker.env	View secret
11648680	Triggered	Generic High Entropy Secret	3e625d2	core/infra/dev_config/content-one.env	View secret
13407071	Triggered	Generic High Entropy Secret	3e625d2	comms/Makefile	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9ac60e6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[audius-infra]

Preview this change https://demo.audius.co/sd-network-cut2

[audius-infra]

Preview this change https://demo.audius.co/sd-network-cut2

[audius-infra]

Preview this change https://demo.audius.co/sd-network-cut2

[rickyrombo]

This looks great

[raymondjacobson]

clean

[audius-infra]

Preview this change https://demo.audius.co/sd-network-cut2

[audius-infra]

Preview this change https://demo.audius.co/sd-network-cut2