[ET-VK] Add Vulkan 1.0 compatibility for extension feature querying

[SS-JIA]

Stack from ghstack (oldest at bottom):

• -> [ET-VK] Add Vulkan 1.0 compatibility for extension feature querying #17160
• [ET-VK] Fix pipeline indexing bug in batch create_pipelines #17159
• [ET-VK] Refactor Context::flush() and make ComputeGraph destructor exception-safe #17158

The previous implementation used vkGetPhysicalDeviceFeatures2 unconditionally,
which is only available in Vulkan 1.1+. Devices running Vulkan 1.0 would fail
to query extension features correctly.

This change refactors PhysicalDevice to detect the API version at runtime and
use the appropriate method:

• Vulkan 1.0: Uses KHR extension functions (vkGetPhysicalDeviceFeatures2KHR)
  obtained via vkGetInstanceProcAddr, with graceful fallback if unavailable
• Vulkan 1.1+: Uses core vkGetPhysicalDeviceFeatures2 directly

Also fixes a bug where shader_int_dot_product_properties was incorrectly
chained into the features linked list instead of being queried separately
via vkGetPhysicalDeviceProperties2.

This PR was authored with Claude.

Differential Revision: D92171361

cc @manuelcandales @digantdesai @cbilgin

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/17160

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 3 New Failures

As of commit 9e59569 with merge base 593775b ():

NEW FAILURES - The following jobs have failed:

• Lint / android-java-format / linux-job (gh)
• pull / android / build-llm-demo / linux-job (gh)
  RuntimeError: Command docker exec -t 3fccbe34922429cd27046bcdb670667b58798d8fb1400758af74e5d8f62ea3a2 /exec failed with exit code 1
• pull / unittest-arm-backend-with-no-deps (test_pytest_models_tosa) / linux-job (gh)
  RuntimeError: Command docker exec -t 3681086c622c996ae4ee0fcba26c50e86ecd120af29ff65b5620b391874ea276 /exec failed with exit code 1

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.