feat(usage overview): Introduce util functions and hook

[isabellaenriquez]

Split out from #103983

Pt 1 of https://linear.app/getsentry/issue/BIL-1817/update-usage-overview-table-with-new-designs

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
12746	1	12745	10

View the top 1 failed test(s) by shortest run time

Subscription > UsageHistory displays soft cap per-category on-demand when relevant

Stack Traces | 1.12s run time

Error: Unable to find an element with the text: Errors (On Demand). This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.

Ignored nodes: comments, script, style
...
    at waitForWrapper (.../sentry/node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@.../dom/dist/wait-for.js:163:27)
    at .../sentry/node_modules/.pnpm/@testing-library+dom@10.4.0/node_modules/@.../dom/dist/query-helpers.js:86:33
    at Object.findAllByText (.../views/subscriptionPage/usageHistory.spec.tsx:438:25)
    at Promise.finally.completed (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:1559:28)
    at new Promise (<anonymous>)
    at callAsyncCircusFn (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:1499:10)
    at _callCircusTest (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:1009:40)
    at _runTest (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:949:3)
    at _runTestsForDescribeBlock (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:839:13)
    at _runTestsForDescribeBlock (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:829:11)
    at run (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:757:3)
    at runAndTransformResultsToJestFormat (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/jestAdapterInit.js:1920:21)
    at jestAdapter (.../sentry/node_modules/.pnpm/jest-circus@30.0.4_babel-plugin-macros@3.1..../jest-circus/build/runner.js:101:19)
    at runTestInternal (.../sentry/node_modules/.pnpm/jest-runner@30.0..../jest-runner/build/testWorker.js:272:16)
    at runTest (.../sentry/node_modules/.pnpm/jest-runner@30.0..../jest-runner/build/testWorker.js:340:7)
    at Object.worker (.../sentry/node_modules/.pnpm/jest-runner@30.0..../jest-runner/build/testWorker.js:494:12)

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[cursor]

Bug: Inconsistent parameter usage in billing metadata hook

The getBilledCategory call uses only product while isAddOn uses parentProduct ?? product. When parentProduct is an add-on category and product is a data category, isAddOn correctly evaluates to true, but getBilledCategory receives the data category instead of the add-on category. This causes getBilledCategory to return the data category unchanged rather than determining the correct billed category for the add-on, leading to incorrect billing metadata.

 

[isabellaenriquez]

this is intentional as we render different things for add ons and their child categories, see #103983 for full usage

[vbro]

LGTM
Curious if this is by any chance inspired by https://www.notion.so/sentry/Sentry-Billing-Platform-26b8b10e4b5d80ef8716f0939c56d6d7. That's the direction the billing is going: from the concept of categories to products.

[brendanhsentry]

noice