We decided to remove generating single-operation spec from build process for GraphQL, since quite often per-operation spec is ~80-90% of the original spec and with hundreds of operation we got x100 increase in build size (e.g. from 2Mb source spec to ~1G build result size), which causes problems on multiple levels starting from network overhead, nginx, DB, backend.

API to get single operation spec will return empty data field for the GraphQL operations in a Get operation details operation (this is done in #399)

We need to generate single-operation spec for GraphQL operations only on-the fly in UI. Incapsulate it in useOperation to be transparent for the rest of the UI code.

This is performance-sensitive operation, need to carefully consider how to make it as performant as possible (e.g. cache intermediate conversion results etc.)