Resolve project name and improve scope filtering in GraphQL Node types

## Overview

Multiple GraphQL Node types (Endpoint, ComputeSessionNode, VFolderNode) expose project as a raw UUID string instead of resolving the human-readable project name. This forces the frontend to make additional queries to display project names, degrading performance and UX.

Additionally, the `vfolder_nodes` query does not properly handle `domain:` and `system:` scope filters for superadmin, unlike the legacy `vfolder_list` query.

## Child Issues

1. **FR-2371** — Endpoint GQL type returns project as ID, cannot resolve project name
1. **FR-2368** — Add project name field to ComputeSessionNode (backend + frontend)
1. **FR-2370** — vfolder_nodes with domain/system scope_id does not list other users' folders for superadmin

## Common Pattern

All three issues require backend GraphQL schema/resolver changes to expose richer data through Node types, aligning them with modern patterns like `SessionV2` which correctly exposes `project: ProjectV2` as a full object reference.

## Expected Outcome

- Node types expose project name directly (no extra queries needed)
- Superadmin can view all folders via vfolder_nodes with domain/system scope
- Frontend admin pages display human-readable project names

JIRA Issue: FR-2407