$sqlquery-export view inlining not supported

[fhnaumann]

Describe the bug
Performing a $sqlquery-export against the server with an inline view definition that is also referenced inside the query field in that request is reported back as invalid with an "undeclared table".

To Reproduce
Request:
POST /$sqlquery-export

Accept:application/fhir+json
Content-Type:application/fhir+json
Prefer:respond-async

{
  "resourceType": "Parameters",
  "parameter": [
    {
      "name": "query",
      "part": [
        {
          "name": "queryResource",
          "resource": {
            "resourceType": "Library",
            "status": "active",
            "type": {
              "coding": [
                {
                  "system": "https://sql-on-fhir.org/ig/CodeSystem/LibraryTypesCodes",
                  "code": "sql-query"
                }
              ]
            },
            "content": [
              {
                "contentType": "application/sql",
                "data": "U0VMRUNUIGNvdW50KCopIEFTIG4gRlJPTSB2ZXJpZnlfcGF0aWVudA==",
                "extension": [
                  {
                    "url": "https://sql-on-fhir.org/ig/StructureDefinition/sql-text",
                    "valueString": "SELECT count(*) AS n FROM verify_patient"
                  }
                ]
              }
            ]
          }
        }
      ]
    },
    {
      "name": "view",
      "part": [
        { "name": "name", "valueString": "verify_patient" },
        {
          "name": "viewResource",
          "resource": {
            "resourceType": "ViewDefinition",
            "url": "https://example.org/ViewDefinition/verify_patient",
            "name": "verify_patient",
            "status": "active",
            "resource": "Patient",
            "select": [
              {
                "column": [
                  { "path": "getResourceKey()", "name": "patient_id" }
                ]
              }
            ]
          }
        }
      ]
    },
    {
      "name": "_format",
      "valueCode": "ndjson"
    }
  ]
}

Returns:

{
  "resourceType": "OperationOutcome",
  "issue": [
    {
      "severity": "error",
      "code": "processing",
      "diagnostics": "SQL references an undeclared table: verify_patient"
    }
  ]
}

Expected behavior
I expect it to resolve the inline resource and return a 202 with a polling location.

[fhnaumann]

Claude bug summary:

The $sqlquery-export operation has a view parameter with a name field that the SQL on FHIR spec defines as "the local table name to use for this view when referenced in any SQL queries in the
same request." However, Pathling completely ignores view.name — it only resolves views by matching the Library's relatedArtifact.resource (canonical URL) to the ViewDefinition's URL. When a request has no
relatedArtifact in the Library, the SQL validator sees an empty allowedLabels set and rejects any table reference.
The fix: parse view.name in resolveSuppliedViews and add named views directly to the ResolvedDependencyGraph as allowed SQL table aliases, bypassing the relatedArtifact requirement.