feat(tracking): add vendor-neutral userInteraction tracking abstraction

[manaswinidas]

Description

Add a concepts/userInteraction module that provides a non-opinionated tracking API via React context. This enables downstream integrations (e.g., ODH with Segment) to inject their own analytics implementation without introducing vendor-specific dependencies upstream.

What's included

File	Purpose
trackingTypes.ts	Event property types + TrackingOutcome enum
UserInteractionContext.ts	React context with dev-mode console logger default
useUserInteraction.ts	Consumer hook
UserInteractionProvider.tsx	Provider for downstream to inject custom api
index.ts	Barrel export

API

Method	Purpose
trackFormEvent(name, props)	Form submit/cancel (outcome, success, error)
trackLinkEvent(name, props)	Navigation/link clicks (from, href, to, section)
trackSimpleEvent(name, props?)	Simple named events
trackPageEvent()	Page view tracking

How downstream uses it

import { useUserInteraction, TrackingOutcome } from '~/concepts/userInteraction';

const { trackFormEvent } = useUserInteraction();

// In a handler:
trackFormEvent('Model Registered', {
  outcome: TrackingOutcome.submit,
  success: true,
});

Downstream (e.g., ODH) injects a Segment-backed implementation via UserInteractionProvider:

<UserInteractionProvider api={segmentImpl}>
  <App />
</UserInteractionProvider>

Design decisions

• No App.tsx change: The context default (dev-mode logger) works without a provider mounted. No dead wrapper needed.
• Reuses existing DEV_MODE: Imports from ~/app/utilities/const rather than redefining.
• Purely additive: 6 new files, zero modifications to existing code. No breaking changes.

Testing

• Unit tests verify provider injection, event routing, and hot-swap behavior
• Type check passes (npx tsc --noEmit)
• Lint passes (npx eslint)

PASS src/concepts/userInteraction/__tests__/useUserInteraction.spec.tsx
  useUserInteraction
    ✓ calls the injected provider implementation instead of the default
    ✓ routes different event types to their respective handlers
    ✓ swaps implementation when provider is re-mounted with a different api

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from manaswinidas. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• clients/ui/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[christianvogt]

Tracking tools should already capture the current URL for all events. It seems redundant to have the caller supply this.

[christianvogt]

What's the different between href and to?

[christianvogt]

These need documentation. It's not clear to me how these should differ from the event name.