✨ [RUM-14241] Implement Assembly with Hooks system

[bcaudan]

Motivation

Allow domain components to declare which data they add to which event format:

this.hooks.registerRum(() => ({
  domain: { attribute: my_value },
}));

this.hooks.registerTelemetry(() => ({
  domain_attribute: my_value,
}));

Changes

• Introduce EventFormat with rum and telmetry (logs and spans will be added later)
• Adapt browser-core hooks to support more than main and telemetry format types
• Extract common event properties to CommonContext
• Use hooks to generate Server events from Raw events with dummy view and telemetry errors
• Extract types for RawData to improve typings

Test instructions

no functional changes, CI should pass

Checklist

• Tested locally (playground)
• Added unit tests for this change.
• Added e2e/integration tests for this change.

[datadog-official]

✅ Code Quality    ✅ Code Vulnerabilities    ✅ Library Vulnerabilities

🎉 All green!

🛠️ No new code quality issues
🛡️ No new code vulnerabilities
📚 No new vulnerable libraries detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5d2362f | Docs | Datadog PR Page | Was this helpful? Give us feedback!}

[cdn34dd]

The PR is well structured, seems good to merge, I would make one change though. I don't think hooks and commonContext belong inside domain. I think of domain as a place for product features, things like Rum, Logs, Traces, Session Replay, etc.

Hooks, Assembly, commonContext I think should place outside as these are part of the event pipeline but not a feature.