Grouped Issue: Asset Scheduling behavior changes based on DAG performance settings (and it shouldn't)

### Apache Airflow version 3.1.0 ### If "Other Airflow 2/3 version" selected, which one? _No response_ ### What happened? ### Asset scheduling behaviors Asset Event triggered DAGs behave one of 3 different ways: 1. A single Asset Event triggers a single DAG Run 2. Multiple Asset Events trigger a single DAG Run 3. Asset Events that haven't triggered a DAG Run, but are older than the last run are silently ignored ### How to make Datasets Behave differently To force behavior 2 & 3 to happen, one can set `max_active_runs=1` and every time the DAG runs it will "consume" (either via behavior 2 or 3) all available Asset Events. To force behavior 1, one must set `max_active_runs` to a high value, and hope that Asset Events are not generated faster than the scheduler runs (or else we fall into behavior 2) It is important to note that the `catchup` argument does not seem to affect this mechanic in any way. ### The main Issue The main issue here is: ### Asset Event Scheduling behaves in very different ways, based on DAG parallelism & Airflow Scheduler performance These things should be unrelated, and as far as I could tell, this behavior is undocumented. ### Linked Issues Other issues that would likely be solved by addressing this issue: https://github.com/apache/airflow/issues/56749 (UI changes) https://github.com/apache/airflow/issues/53896 (distinct DAG Run per Asset Event) https://github.com/apache/airflow/issues/50890 (want catchup on Assets) https://github.com/apache/airflow/issues/56691 (distinct DAG Run per Asset Event) https://github.com/apache/airflow/issues/56050 (Max active runs = 1 changes behavior) https://github.com/apache/airflow/issues/55956 (Force separate Events) https://github.com/apache/airflow/issues/47398 Unclear issues that may be related: https://github.com/apache/airflow/issues/56541 ? (unclear) https://github.com/apache/airflow/issues/42015 ? (unclear) ### What you think should happen instead? In my professional setting we use both behav…