Custom profiles

Let's assume that the arbitrary selection function from #58 is available.

It might be useful to be able to setup different profiles for different variations of the target element.

For example:
The whole domain model of a `Vehicle` (i.e., the specification files in `GraphQL` contains:
- 100 object types
- 1000 Fields across those objects

But in my system or use case I have different types of vehicles. For instance, some have 2 doors, whereas others have 4, etc.

Does it make sense to allow the speficiation of different profiles, like:

- `MyVehicleModel_X`
- 50 objects (selected from the 100 of my model)
- 300 properties (selected from the selected 50 objects)
- `MyVehicleModel_Y`
- 25 objects (selected from the 100 of my model)
- 67 properties (selected from the selected 25 objects)

Start by reading issue #58, since this proposal assumes its arbitrary selection function is available. Clarify how profiles select objects and fields from a GraphQL specification, then define the expected behavior for the example vehicle profiles and how completion would be verified.

Written by the indexing model from the issue text.