chore - rename InQL to IncQL

[dannymeijer]

Summary

Renames the package, repository-facing identifiers, docs, RFCs, workflow metadata, and query-block companion crate from InQL to IncQL. This aligns the public brand, the lowercase technical slug, generated metadata, CI paths, and the GitHub repository name.

Type of change

• Bug fix
• New feature
• Refactor / maintenance
• Documentation
• CI / tooling
• RFC (adds/updates docs/rfcs/*)

Area(s)

• Package & tests
• Specification (RFCs)
• Documentation
• Automation & repo config
• Other

Key details

• User-facing behavior: The product, package, documentation, and RFC filenames now use IncQL and incql.
• Internals: Renamed the package manifest, metadata helper, vocabulary companion crate, locks, CI paths, examples, and repository references consistently.
• Risks: The package slug is intentionally breaking for consumers that still declare or import inql; downstream consumers must move to incql.

Testing / verification

• make ci (format, style, companion tests, registry metadata, library build, and 269 tests)
• make fmt-check
• test-style check
• vocabulary companion tests
• Manual verification described below

Manual verification notes:

• git diff --check passed.
• A repository-wide inql text/path audit returned no matches.
• The generated public-consumer project type-checked and executed its query, quality, and governance smoke program successfully.
• Corrected the generator payload marker to the renamed INCQLGEN1 value before publishing the branch.

Docs impact

• No docs changes needed
• Docs updated
• Docs follow Divio intent (tutorial/how-to/reference/explanation) where applicable

Checklist

• I kept public docs user-focused and moved internals to contributing docs when appropriate
• I avoided duplicating canonical install/run instructions in multiple places
• I added/updated tests where it materially reduces regressions