feat: pft telemetry @W-21233151

[mshanemc]

What does this PR do?

send telemetry via o11y for PFT
records only commandExecution
sets the endpoint/PFT id for all of our extensions
support for 2PP extensions is them adding the correct props to pjson

What issues does this PR fix or reference?

@W-21233151@

QA notes: be sure to deactivate dev mode for testing locally

[jonnyhork]

I ran into a build error with npm run vscode:bundle, Claude offered some notes:

npm run vscode:bundle fails because the PR imports o11y_schema/sf_pdp in o11yReporter.ts and o11ySpanExporter.ts, but the o11y_schema package does not export sf_pdp. The Jest mock at config/__mocks__/o11y_schema_sf_pdp.js makes unit tests pass; esbuild fails when bundling extensions.

Fix: Add an alias in the bundle configs so the import resolves to the existing mock at bundle time:

1. scripts/bundling/web.mjs — add to commonConfigBrowser.alias:

'o11y_schema/sf_pdp': join(__dirname, '../config/__mocks__/o11y_schema_sf_pdp.js'),

2. scripts/bundling/node.mjs — import path/join and add an alias block:

alias: {
  'o11y_schema/sf_pdp': join(__dirname, '../config/__mocks__/o11y_schema_sf_pdp.js'),
}

Note: The mock exports { pdpEventSchema: {} }. Verify that @salesforce/o11y-reporter's logEventWithSchema works at runtime with this schema when running the web extension.

[jonnyhork]

If these orgId and deHubId are not defined, we would still send undefined:undefined right?

Is there a way to omit the property if not defined instead? Not a big deal, but undefined tends to feel like an error to me or and possibly others.

[mshanemc]

no, they show up as empty strings because of line 103/105

[mshanemc]

you're going to love TS! because the types on the pft method are string for those props, it won't let you pass in undefined. You don't have to worry about stuff like that.

[there's also an eslint rule to keep people from using null/undefined stuff in template literals...we don't have it on but we could]

[jonnyhork]

ah those lines were hidden/collapsed by GitHub...

[jonnyhork]

You demo video looked good in superset, I did not look for events myself, I have used Superset before but I'd have to dig up the links and query etc.

[mshanemc]

I ran into a build error with npm run vscode:bundle, Claude offered some notes:

npm run vscode:bundle fails because the PR imports o11y_schema/sf_pdp in o11yReporter.ts and o11ySpanExporter.ts, but the o11y_schema package does not export sf_pdp. The Jest mock at config/__mocks__/o11y_schema_sf_pdp.js makes unit tests pass; esbuild fails when bundling extensions.

Fix: Add an alias in the bundle configs so the import resolves to the existing mock at bundle time:

1. scripts/bundling/web.mjs — add to commonConfigBrowser.alias:

'o11y_schema/sf_pdp': join(__dirname, '../config/__mocks__/o11y_schema_sf_pdp.js'),

2. scripts/bundling/node.mjs — import path/join and add an alias block:

alias: {
  'o11y_schema/sf_pdp': join(__dirname, '../config/__mocks__/o11y_schema_sf_pdp.js'),
}

Note: The mock exports { pdpEventSchema: {} }. Verify that @salesforce/o11y-reporter's logEventWithSchema works at runtime with this schema when running the web extension.

oh, that was interesting. I got it to work by unpinning the o11y versions (now ^) so they can all use latest. Previously, they'd have their own version in package-level node_modules and that pdp was on the package-level but not the repo-level o11y_schema. I think that's a lot cleaner than Claude's hacky idea

[jonnyhork]

Bundling work for me now.

[jonnyhork]

ah those lines were hidden/collapsed by GitHub...