Enable triggerer queues

[zach-overflow]

---

Closes: #33818

What?

• Adds optional support for "trigger queues", which allows a given triggerer to consume from a user-configured subset of triggers.
  • Adds a trigger_queues instance attribute to the Triggerer, which comes from the triggerer.consume_trigger_queues config option, or the --consume-trigger-queues CLI option.
  • Adds a trigger_queue instance attribute to the Trigger, which may either be explicitly set on initialization, or will use the new triggerer.default_trigger_queue config as a default.

Why?

• AIP-67 (multi-tenancy support), to enable team-specific triggerer assignment.
• More generally, and not necessarily specific to multi-tenancy use-cases, to allow for other trigger strategies which may require distinct sets of triggerers.

Remaining TODOs before removing "Draft" status

• Figure out why alembic is not detecting a change to the trigger table / not auto-generating a new revision.
• Run db tests once an alembic revision can be generated.
• Add newsfragment file summarizing this change.

Testing

• breeze testing core-tests airflow-core/tests/unit --skip-db-tests --use-xdist
• breeze testing providers-tests --run-in-parallel --skip-db-tests
• prek

[zach-overflow]

I would expect alembic to have detected this change, but whenever I follow this contributor doc section, I get the following issue:

This happens despite running breeze --backend postgres --db-reset rebased off main latest, so any thoughts on what I might be missing are appreciated!