feat(device): applications ask for the device features their shaders use

Device
- Device::Initialize(required, optional) takes DeviceFeatures, the five
  core feature structs vulkan10 to vulkan14. The library enables only what
  its own shaders and code use. Device::enabledFeatures says what was
  enabled, supportedFeatures what the GPU has, apiVersion the version in
  use.
- shaderInt16, shaderFloat16, storageBuffer16BitAccess, scalarBlockLayout
  and the uniform-buffer, storage-buffer and storage-image non-uniform
  indexing bits are no longer enabled for everyone. An application whose
  shaders take uint16_t spec constants passes
  {.vulkan10 = {.shaderInt16 = VK_TRUE}}. scalarBlockLayout stays on with
  the NVIDIA workaround, whose TLAS address may sit in a struct's tail
  padding.
- Every GPU is weighed before one is chosen: Vulkan 1.3, the swapchain and,
  below 1.4, maintenance5 extensions, the library's needs, the required
  features. One that can't run the application is skipped, saying why when
  it ranks higher. A CPU device runs it only when nothing else is listed,
  and CRAFTER_GRAPHICS_DEVICE never falls back. A GPU two drivers both list
  is tried through each.
- When no GPU qualifies, Initialize throws naming each GPU's gaps. It
  destroys the instance it made, before any Wayland connection, so it can
  be called again asking for less.
- maintenance5 is vulkan14's on a 1.4 GPU and VK_KHR_maintenance5's below.
  CRAFTER_GRAPHICS_NO_VULKAN_1_4 runs as a 1.3 application, to exercise
  that path on a 1.4 GPU.
- VK_KHR_spirv_1_4 and VK_KHR_shader_float_controls, core since 1.2, are no
  longer enabled, nor VK_EXT_shader_atomic_float, which was enabled without
  its feature struct. memoryDecompression's feature bit is queried before
  it is enabled.

Shaders
- VulkanShader checks a module's capabilities, declared directly or
  implicitly, against the enabled core features, the GPU's subgroup
  operations and the optional groups, and throws naming the field to pass,
  or saying the GPU lacks it. The tables are generated from vk.xml and
  SPIR-V's grammar.
- WorkaroundNvidiaAS::Patch sized a row-major matrix push member by its
  columns, so the TLAS address could land inside it.

Window
- The swapchain format is one whose own feature flags allow storage reads
  and writes without a format, which since Vulkan 1.3 each format says for
  itself; shaderStorageImageRead/WriteWithoutFormat are no longer required.

Tests
- DeviceFeatures: ResolveFeatures, ChooseDevice and CheckShaderCapabilities,
  without a GPU.
- FeatureRequests: required and optional features end to end, the 1.3
  path, and a retry after a refusal.
- PushConstantRewrite: a row-major mat3x4 push member.
- HeapASRead, HeapDynamicIndexHit, RTPassPushData and the ray-tracing
  examples ask for the features their shaders use.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

README.md

@@ -89,10 +89,25 @@ shaded through an intersection shader with an any-hit cut-out.
   `VK_EXT_descriptor_heap`; pipelines are created with
   `VK_PIPELINE_CREATE_2_DESCRIPTOR_HEAP_BIT_EXT` so there are no
   descriptor-set layouts and push constants travel via
-  `vkCmdPushDataEXT`. The heap, ray tracing and device-fault extensions
-  are optional groups, detected at start-up
+  `vkCmdPushDataEXT`. Needs Vulkan 1.3. The heap, ray tracing and
+  device-fault extensions are optional groups, detected at start-up
   (`Device::descriptorHeapSupported`, `rayTracingSupported`,
-  `deviceFaultSupported`).
+  `deviceFaultSupported`). Device features split by who uses them: the
+  ones the binding model and the library's own shaders need are the
+  library's to enable; arithmetic, storage and layout features an
+  application's shaders use (`shaderInt16` for a `uint16_t` spec
+  constant, `scalarBlockLayout`, fp16, 16-bit storage) are the
+  application's to ask for, as core feature structs:
+  `Device::Initialize({.vulkan10 = {.shaderInt16 = VK_TRUE}})`. A second
+  argument takes features to use where the GPU has them, and
+  `Device::enabledFeatures` says which it got. A GPU that can't run the
+  application is skipped. `VulkanShader` refuses a module that declares,
+  directly or implicitly, a capability whose core feature, subgroup
+  operation or optional group (ray tracing, the descriptor heap) is off,
+  naming the field to pass or saying the GPU lacks it. Capabilities only
+  an extension the library never enables could allow are left to the
+  driver and the validation layer, as are layout rules
+  (`scalarBlockLayout`), which have no capability.
 - **DescriptorHeapVulkan / DescriptorHeapWebGPU** — bindless slot
   allocators. Vulkan side allocates image/buffer/sampler slots in a
   `VK_EXT_descriptor_heap`; WebGPU side resolves slots to JS-side