Fix: Reduce performance hit for not using automatic interface description

[johannwagner]

The introduction of Automatic interface descriptions gave cosmo a measurable performance hit. In WOBCOMs netbox, we are waiting for the result of cosmo to allow the user to close the change. It currently takes about 15 seconds to get a full run done, which could be done in 5 seconds, if we omit all the data related to link_peer, connected_endpoints in the Device query and use the Dummy Tobago insert.

There are two ways of implementing this feature:

1. Extract link_peer and connected_endpoints data from DeviceQuery into a seperate query, for example LinkInformationQuery, and use a dummy for validate mode.
2. Add a switch to DeviceQuery to remove the not wanted fields from the GraphQL query.

I would favor Option 1, there is already infra around this.

Validate mode would then not insert TobagoQuery and LinkInformationQuery into the data fetch queue but some dummies to insert null values. Those null values then need to be handled within the code.

This should get us back to around 5 seconds of fetch time.

[loulecrivain]

remark: the auto interface description is an enabled-by-default feature, that we can disable explicitly for check run, rather than having a "fasttrack" feature switch which would not be terribly descriptive of what it does or doesn't do.

we already have code for auto interface description feature switch, what we could do is extend this instead to disable more code paths and avoid unnecessary fetches.