auto label is removed for flutter/engine, pr: 36769, due to - The status or check suite Mac Host Engine has failed. Please fix the issues identified (or deflake) before re-applying this label.

FYI I'm working on rolling to the latest ANGLE version in this WIP PR: #36389. Here are blockers I'm aware of:

1. ANGLE is affected by an MSVC bug, we need to update to VS 2019 or newer: angleproject#7693
2. Updating to VS 2019 exposes a bug in EventChannel which causes framework tests to fail, see: [Windows] Fix stack corruption issues flutter#113135 (comment)
3. The latest version of SPIRV Cross generates invalid shader programs, breaking engine tests. See: GLSL's merge to direct for loop is regressed KhronosGroup/SPIRV-Cross#2031
4. Lots of smaller miscellaneous things, see: Roll ANGLE, vulkan-deps, and shaderc #36389

My recommendation would be to try to roll to the non-latest versions to avoid these issues.

I think I've found the earliest ANGLE commit that has the vulkan-deps commit we needed. I did some searching with git grep and git rev-list. I probably could have rolled vulkan-deps out of sync with ANGLE, but trying to avoid that if this can pass CI.

@loic-sharma I'm taking a slightly different approach to resolving the unguarded availability -we don't actually use the Metal EXT stuff so I'm just undefining that before including vulkan.h. I'll file something upstream in vulkan headers to see if we can get availability guards to flow through eventually.

Unfortunately this commit is making Windows unhappy. Going to try to just rev vulkan-deps to the earliest commit that has the change that fixes the macOS deprecations when building for Android.

Just revving vulkan-headers a little bit seems to be passing CI. That's enough to fix one of our problems.