Break the route<->component cycles without touching createFetcherSubmitHook or
use-request.ts, and without generated +types:
- The data-access hooks that descendants import are moved out of route entry files
into neutral modules that own both the interface and the hook, so route files are
no longer shared-hook modules:
* ui/hooks/use-project-loader-data.ts (ProjectLoaderData + useProjectLoaderData)
* ui/hooks/use-mock-route.ts (MockRouteLoaderData + useMockRouteLoaderData; patcher kept)
Each route's clientLoader conforms to the interface via 'satisfies', so the type
has a single source and cannot drift; consumers import the named hook.
- cycle route.update -> content-type-dropdown -> use-request -> route.update is cut
at the route->component edge by moving the pure updateMimeType/newBodyGraphQL
helpers to ui/utils/request-mime-type.ts (use-request/createFetcherSubmitHook untouched).
- grpc: GrpcMessage/GrpcRequestState moved to ui/utils/grpc.ts.
- useWorkspaceLoaderData is left in place (route.workspace is not in any cycle).
## Summary
- Replaces the madge-based `check-cycle-references` with a `dependency-cruiser`-based check, cruised once per npm workspace package.
- Keeps the checker, dependency-cruiser config, and known-cycle baseline together under `scripts/circular-references/`.
- Uses a committed baseline to grandfather existing cycles while failing on new cycles and stale baseline entries.
- Cleans the existing `insomnia-inso` type cycle by using `insomnia-data`'s `AllTypes` instead of importing the database container type.
- CI explicitly uses Bash for correct `tee`/pipeline failure propagation, safely handles skipped checks, and posts a PR report.
- Dropped `madge`/`.madgerc`, added `dependency-cruiser`.
Bingbing