sql: swap CODEOWNERS between SQL Foundations and SQL Queries

[spilchen]

This is the full ownership swap between the SQL Foundations and SQL Queries teams. IMPORT was previously moved to SQL Foundations in #167978.

Moving to SQL Queries:

• INSPECT
• Row-level TTL
• Temp tables
• Partitioning (drop partition)
• Multi-region

Moving to SQL Foundations:

• COPY
• Stored procedures
• UDFs
• Triggers

Release note: None
Epic: none

[trunk-io]

😎 Merged successfully - details.

[cockroach-teamcity]

This change is 

[blathers-crl]

Detected infrastructure failure (matched: ). Automatically rerunning failed jobs. (run link)

[blathers-crl]

Detected infrastructure failure (matched: ). Automatically rerunning failed jobs. (run link)

[fqazi]

@fqazi reviewed 9 files and all commit messages, and made 1 comment.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on mw5h).

[blathers-crl]

Metrics change detected

This PR adds or updates one or more CRDB metrics. If you want these metrics to be exported by CRDB Cloud clusters to Internal CRL Datadog and/or included in the customer metric export integration (Essential metrics for standard deployment, and Essential metrics for advanced deployment), refer to this Installation and Usage guide of a CLI tool that syncs the metric mappings in managed-service. Run this CLI tool after your CRDB PR is merged.

• The CLI opens a PR in managed-service with the required config changes.
• Please track that PR and ensure it merges so your metrics become available to CRDB Cloud clusters.

Note: Your metric will appear in Internal CRL Datadog only after the managed-service PR merges and the new OTel configuration rolls out to at least one cluster running a CRDB build that includes this metric.

Docs: cockroach-metric-sync

Questions: reach out to @obs-india-prs

[mw5h]

@mw5h made 1 comment.
Reviewable status: complete! 2 of 0 LGTMs obtained (waiting on spilchen).

[spilchen]

TFTR!

/trunk merge

[blathers-crl]

Encountered an error creating backports. Some common things that can go wrong:

1. The backport branch might have already existed.
2. There was a merge conflict.
3. The backport branch contained merge commits.

You might need to create your backport manually using the backport tool.

---

merge conflict cherry-picking 553a638 to blathers/backport-release-24.3-168323

Backport to branch release-24.3 failed. See errors above.

---

merge conflict cherry-picking 553a638 to blathers/backport-release-25.2-168323

Backport to branch release-25.2 failed. See errors above.

---

merge conflict cherry-picking 553a638 to blathers/backport-release-25.4-168323

Backport to branch release-25.4 failed. See errors above.

---

merge conflict cherry-picking 553a638 to blathers/backport-release-26.1-168323

Backport to branch release-26.1 failed. See errors above.

---

merge conflict cherry-picking 553a638 to blathers/backport-release-26.2-168323

Backport to branch release-26.2 failed. See errors above.

---

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}