Should placecontext drop "context" from its name?

## What are the schemas that are affected by the issue
placecontext

## What are examples of products that are impacted by the issue

Unified Edge Gateway
Data Platform Web SDK
Possibly others

The `placecontext` schema seems to be the only context schema with "schema" in its name. This makes it inconsistent when residing alongside other contexts. This inconsistency is cascading through to APIs exposed by the Unified Edge Gateway and any SDK that use the gateway, among other things. Is this intentional or an oversight? Can/Should we change it?

Start by reviewing the placecontext schema alongside the other context schemas and compare how their names are exposed. Trace the naming impact on the Unified Edge Gateway and Data Platform Web SDK, then document whether the inconsistency is intentional and what a rename would affect.

Written by the indexing model from the issue text.