Move context augmentation to Page enrichment

[zikaari]

Part of https://segment.atlassian.net/browse/LIBWEB-1426

Since Page Enrichment is no longer just enriching "page" events, with page information, I wanted to rename this to something generic like "Context Enrichment", but wasn't certain if this is safe. Open to discussion.

The original implementation suggests something about falling back to "options" if "context" is not there. Not sure what that means, so please help me identify what's the intended outcome of that design so I can double-check that behaviour is not impacted.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4614b24

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@segment/analytics-next	Minor
@segment/analytics-core	Patch
@segment/analytics-node	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[silesky]

@zikaari This PR is a big improvement architecturally! Thanks for taking this on.

I wanted to rename this to something generic like "Context Enrichment", but wasn't certain if this is safe. Open to discussion.

Cool! Yeah, I see this plugin is about augmenting the event with information from the user's environment-- so maybe EnvironmentAugmentation plugin would be a good candidate -- but "page" can also be interpreted as a kind of word for environment :-)

I mainly don't like the word 'enrichment' because this plugin isn't a type:enrichment plugin -- so it's v confusing.

[zikaari]

@pooyaj Do you know any dangers of renaming a plugin on top of your head? Not just the symbol name, but also Plugin.name property.

If you don't feel confident, we can leave renaming it to some other time.

[silesky]

@zikaari change to core package (campaign interface) should have a another changeset 😉