[usage] Implement charge dispute handling - WEB-94

[easyCZ]

Description

Uses the User & Team service to block owners when a dispute is raised.

• Uses go-vcr to record a Stripe response with a hook to drop authorization

Related Issue(s)

• Depends on [public-api] Setup handler for charge.dispute.created #17034
• Depends on [usage] Add server address to config - WEB-94 #17094

How to test

Release Notes

NONE

Documentation

Build Options:

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

/hold

[atduarte]

/reviewpad summarize

[reviewpad]

AI-Generated Pull Request Summary: This pull request includes changes to multiple files, mostly removing redundant whitespaces and cleaning up unnecessary lines. Significant updates include adding new dependencies, modifying the configuration logic, and updating the billing system to handle charge disputes. New utility functions ClusterAddress and ClusterURL have been added to the net.go file for working with service addresses in a Kubernetes cluster, while multiple test functions have been introduced to support added functionality. Overall, these changes improve code style consistency, maintainability, and enhance the billing system's handling of charge disputes.

[easyCZ]

/hold for dependency

[svenefftinge]

LGTM - Also nice testing setup!
FWIW it doesn't feel great to have a bidirectional dep between server and usage but I guess we'll have to live with it given our architecture. 🤷

[easyCZ]

FWIW it doesn't feel great to have a bidirectional dep between server and usage but I guess we'll have to live with it given our architecture. 🤷

Agree. I'm hoping we can fix the "leadership election" part and merge usage with PAPI. It doesn't remove the bi-directionality, but at least it consolidates it closer to the desired architecture.

[easyCZ]

/unhold