test: correct comment on label-filter rationale (#104)

The previous comment claimed the test's setup CREATE PROPERTY GRAPH
job did not carry the sdk_feature='ontology-gql' label. That was
factually wrong: setup goes through
OntologyPropertyGraphCompiler.create_property_graph() (line 387),
which does carry the label.

The test logic was already correct — the setup job is excluded by
the post-setup timestamp captured in step 2, not by the label
filter. The label filter excludes user-authored raw SQL DDL jobs
(without SDK labels), which is its actual purpose. Only the comment
needed to change.

No code change.

Author: caohy1988

tests/test_integration_ontology_binding.py

@@ -449,10 +449,12 @@ def test_skip_property_graph_issues_no_create_graph_job(
     #      the regression in either dataset.
     #   4. sdk_feature='ontology-gql' label — only SDK-issued
     #      property-graph jobs carry this label
-    #      (ontology_property_graph.py:465), so unrelated user-
-    #      authored CREATE PROPERTY GRAPH DDLs (including the test's
-    #      own setup job in step 1, which was not labeled this way)
-    #      do not trip the assertion.
+    #      (ontology_property_graph.py:465). The setup CREATE PROPERTY
+    #      GRAPH job in step 1 *also* uses this label (it goes through
+    #      OntologyPropertyGraphCompiler.create_property_graph()), but
+    #      it is excluded by the post-setup timestamp captured in
+    #      step 2. User-authored raw SQL DDL jobs without SDK labels
+    #      are excluded by this label filter.
     region_qual = f"`region-{_LOCATION.lower()}`"
     jobs_query = f"""
     SELECT job_id, query, creation_time