Investigate how to provide component slicing on top of endpoints slicing

[sebastienlevert]

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?

[baywet]

I think we could deliver this with a couple of restrictions:

1. only works for components schema, not for inline schemas
2. only allows you to trim properties of models (and associated models if they become "isolated" because of that), or entire models, not enum members, composed type member types, etc...

--whatever microsoft.graph.servicePrincipal --whatever microsoft.graph.user#memberOf

Would trim the service principal type, and any reference to it, as well as the memberOf property from user (and if we assume that property was the only reference to group, group would also be trimmed off)

We'd need to come up with a parameter name.

Now the question is: do we need any of that considering it requires some advanced understanding of kiota/OpenAPI and considering we're talking about overlays support which would allow you to do the exact same thing?