Docs: no page says which query language to use; example 02 leads graph queries with the SQL graph syntax #263

No page of the bindings docs says which query language to use. how-to/databases-and-queries.adoc shows SQL and openCypher side by side under "Write and query" but never says when to pick which, and example 02 (02_social_network_graph.py) leads its graph queries with the older SQL graph syntax (MATCH {type: Person, as: p}, out(), outE()) and prints it first in its comparison.

A reader who starts from the example learns the SQL graph syntax first, although openCypher, a graph pattern language shared by many databases and close to the ISO GQL standard, is the better fit for graph patterns, and plain SQL stays the language for documents and tables. Found in the docs audit of 2026-11-04 (item M3), alongside the SQL and Cypher discussion in ArcadeData/arcadedb#11292.

Scope of the fix: a short "Which query language" paragraph on that page (openCypher for graph patterns and traversals, SQL for documents, tables, schema, inserts and aggregates, the SQL graph syntax supported but not recommended for new code), links to the main ArcadeDB SQL and openCypher references instead of repeating them, and example 02 led by openCypher. Examples 05 and 06 also lead with SQL MATCH; they need their own run on the small dataset before their text changes, so they are left for a follow-up.