r7.0.6's release process was just kicked off, and it inadvertently caused the api_version_compatibility task on the commit queue of mongodb-mongo-master and mongodb-mongo-v7.3 to fail. (example failure: https://evergreen.mongodb.com/task_log_raw/mongodb_mongo_v7.3_commit_queue_test_api_version_compatibility_patch_7636492d4f8a7243faedb54ae0d5f4933a29a8c0_65d54e250305b9759fbb1acc_24_02_21_01_14_08/0?type=T#L3014)

The issue appears to be due to the $queryStats aggregation stage being included partially backported in the 7.0.6 release (PM-3120). I'm seeing the r7.0.6 tag on 66cdc1f2817, which comes after 551de6ae06d (SERVER-86432 Query Stats Backport to 7.0 Batch #4), but before 414df57c19b (SERVER-86523: Backport Query Stats to 7.0 Batch #5) and af54ee77636 (SERVER-86652: Query Stats Backport to 7.0 Batch #6). There are also a number of other commits that landed on the 7.0 branch in the last two weeks after where the r7.0.6 tag is.
 
This issue in particular seems to be caused by the fact that the later versions have the following access check for $queryStats, but r7.0.6 does not:

+                - privilege: # $queryStats
+                    agg_stage: queryStats
+                    resource_pattern: cluster
+                    action_type: queryStatsReadTransformed

That said, there could be other issues given that the feature wasn't completed backported yet.

To unblock master and the other branches' commit queues, I believe api_version_compatibility can be disabled temporarily, since the issue appears to be in r7.0.6 rather than in later releases, but the root issue would still need to be addressed in order to re-enable the test.