[customer analytics] Opportunities tab: confirm salesforce access-denied errors aren't captured

Summary

Low confidence / needs confirmation. A few You don't have access to table salesforce.opportunity exceptions are captured on the accounts page, even though the Opportunities tab is designed to treat a denied/absent Salesforce table as an expected empty state (not a reported error). Code review suggests the isExpectedMissingTableError matcher already covers the real (enriched, multi-line) message, so these captures most likely originate from a different path — e.g. the initial accountsRetrieve call failing, or the shared loaders onFailure. This needs a captured stack trace to confirm before fixing.

Part of #68887.

Details for coding agents

What was checked

• isExpectedMissingTableError uses substring matching that covers both the bare message and the production-enriched form (… \nTables referenced: salesforce.opportunity), and the "expected" branch does not capture. So the Opportunities query path itself should already be silent for this error.
• Therefore the captured events likely come from: (a) the first try/catch around accountsRetrieve (fetching sfdc_id) which captures unconditionally, or (b) the shared loaders onFailure in initKea.ts — see also the AbortError/noise issue.

Proposed next step / fix

1. Pull a stack trace for one of these $exceptions to confirm the capture site.
2. If it's the expected-error path after all, widen the guard (also gate on HTTP status, not just message text) and add a test for the enriched multi-line message (current test only asserts the bare string).
3. If it's accountsRetrieve, make that catch skip the expected access-denied/missing-table case too.

References

• products/customer_analytics/frontend/components/Accounts/accountOpportunitiesLogic.ts:43-49 (isExpectedMissingTableError), :64-71 (accountsRetrieve try/catch), :68,99 (captureException)
• products/customer_analytics/frontend/components/Accounts/accountOpportunitiesLogic.test.ts:62 (test uses bare message only)
• posthog/hogql/metadata.py:199 (enrich_hogql_validation_error adds the Tables referenced: suffix)
• frontend/src/initKea.ts:128-130 (shared onFailure capture)

Start with the stack trace for a captured exception, then inspect accountOpportunitiesLogic.ts around isExpectedMissingTableError, accountsRetrieve, and captureException. Compare the existing test in accountOpportunitiesLogic.test.ts with the enriched error described in metadata.py, and check initKea.ts for shared capture behavior. Done means the capture path is confirmed and the appropriate guard or test is updated.