Request reducer

In v3, there may be a new reducer that stores request information separately from any resource. **The request info on resources is not going away.** It will just be duplicated for now.

This issue is for discussions around this new feature.

Current open questions:

- Is it too confusing to have resource and request plugins?
- Should requests store list info as well?

---

I'm not 100% certain that I need this reducer to be separate. Tying the requests to resources works well enough. And a `` component could just have the `resourceName` specified there, as well...

I'll need to think more on this

---

After reading the roadmap, I think I may be able to hold off on this change for now. Scoping by resource isn't the _worst_ given that most RESTful APIs tie endpoints to one resource. And as I've demonstrated with the v3 work so far, it is easy to add in later in a non-breaking way. Maybe I should skip this change for v3...

Start with the v3 roadmap and the existing resource reducer, request handling, plugins, and component mentioned in the issue. Resolve whether a separate request reducer is still needed and how it should handle list information. The work is done only after the scope and design are decided, since the issue currently defers the change.

Written by the indexing model from the issue text.