Investigate how to provide component slicing on top of endpoints slicing

As depicted in #4440, it would be useful to allow developers to define the specific properties from the referenced components. For instance, if I'm using the `/users` endpoint on Microsoft Graph, I should be able to say that I only care about the `displayName` and the `id` of the component. The rest will not be useful for my scenarios so I'd rather not have them. This will also limit the number of components retrieved and generated as models (no reference to them so they would become useless).

The big questions:

* Technically, is that even doable and a good idea?
* How to provide a DevX that makes sense and doesn't required complex configurations
* What do we do in cases where 2 paths are using the same component? Do we merge the config for both? Do we have 2 models?

Start by reviewing issue #4440 and the component and endpoint slicing concepts described here, using the Microsoft Graph /users example as a concrete case. Determine whether component property selection is technically feasible, define a simple developer experience, and document how shared components should behave when referenced by multiple paths.

Written by the indexing model from the issue text.