Support a user-defined private state for continuous service requests

Continuous services may fulfill requests over the course of multiple schedule cycles. To implement the service, users might want to store a state data structure that persists across the cycles. Each state instance should be associated with exactly one ongoing request.

We should add a fourth generic parameter called State to ContinuousServiceKey and ContinuousQuery. It would have a default argument of (), which should preserve backwards compatibility for the API.

To begin we will require the State to implement Default so we can default-initialize the value upon a new request coming in. We could consider requiring it to implement FromWorld instead, or come up with our own trait similar to FromWorld that also provides information about the source and provider entity as well as the initial request data, all alongside a &mut World.