Deprecate Context and Job Agents

[futursolo]

This discussion proposes to deprecate Context and Job agents.

The current state of these two agent kinds are kind of "awkward" as now we have <ContextProvider /> & use_reducer API available. Contexts and hooks are easier to understand, better documented, and can achieve the same goal as these agents.

In addition, agents do not have a good way to access contexts provided by <ContextProvider /> as they do not have a place in the VDom.

Job Agent

Job agents can be replaced by an internal state machine mechanism (implemented with message) inside struct components or hooks API inside function components.

Context Agent

Context agents can be replaced with hooks / state machine of a parent component + <ContextProvider />.

[futursolo]

This idea came up when I was thinking of purposing a <AgentContextProxy<T> /> type to help agents gain access to contexts and realised that agents can be replaced with the new contexts and hooks API. Hence I purposed them to be removed instead.

[voidpumpkin]

Looks like a logical improvement to me.

As long as we provide a tutorial how to migrate said agents to context api.