[FEATURE] Implement Tracking for JS (Server)

[toddbaert]

Implement tracking as per spec: open-feature/spec@cd99c35

Functional requirements:

• implement all the features described here

Non functional requirements:

• use as many existing abstractions and implementations as possible
  • ie: tracking event details should likely use similar underlying functionality to evaluation context / structure
• provider interface(s) are modified to optionally support tracking; not all providers will support it
• associated testing and README entry (see markdown snippet below)
• no breaking changes

README addition (be careful to correctly link to #hooks and #providers and update the code snippet for the language in question

### Tracking

The tracking API allows you to use OpenFeature abstractions and objects to associate user actions with feature flag evaluations.
This is essential for robust experimentation powered by feature flags.
For example, a flag enhancing the appearance of a UI component might drive user engagement to a new feature; to test this hypothesis, telemetry collected by a [hook](#hooks) or [provider](#providers) can be associated with telemetry reported in the client's `track` function.

```{language-in-question}
// flag is evaluated
client.getBooleanFlag('new-component-style');

Note that some providers may not support tracking; check the documentation for your provider for more information.

...

// new feature is used and "track" function is called 
useNewFeature();
client.track('new-feature-used');

[wichopy]

@toddbaert I could give this a shot. Is reading the spec the best place for understanding whats needed? Is there a slack thread / meeting recording that may give more context?

[beeme1mr]

Hey @wichopy, I think @toddbaert is actively working on this, but feel free to help with the review. By the way, would you be interested in joining the org? It's the first step in becoming a maintainer and makes it easier for use to @ mention you.

[wichopy]

I'd love to join!