TEAMS: use workflow for SQL Queries issue triage

[mgartner]

The SQL Queries team now uses Github Projects v2. This commit updates
TEAMS.yaml and .github/workflows/add-issues-to-project.yml so that
issues are assigned to the correct project for triage.

Epic: None

Release note: None

[cockroach-teamcity]

This change is 

[DrewKimball]

Reviewed 1 of 1 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @michae2)

[michae2]

Reviewed 1 of 2 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: complete! 2 of 0 LGTMs obtained (waiting on @mgartner)

[mgartner]

bors r+

[craig]

Build failed (retrying...):

• Bazel Essential CI (Cockroach)

[mgartner]

bors r+

[craig]

Already running a review

[mgartner]

bors r+

[craig]

Already running a review

[craig]

Build succeeded:

• Bazel Essential CI (Cockroach)

[rail]

blathers backport release-23.1
so roachtest gets the fresh copy of TEAMS.yaml and stops triaging to the old project

[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.

---

error creating merge commit from 9a1b230 to blathers/backport-release-23.1-107498: POST https://api.github.com/repos/cockroachdb/cockroach/merges: 409 Merge conflict []

you may need to manually resolve merge conflicts with the backport tool.

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

---

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