Some supported formats are not included in the mapping appendix

Although most (if not all) of them do not have direct equivalents in other APIs, the JSON file should still provide type size and block dimensions for them.
```
VK_FORMAT_G8B8G8R8_422_UNORM
VK_FORMAT_B8G8R8G8_422_UNORM
VK_FORMAT_R10X6_UNORM_PACK16
VK_FORMAT_R10X6G10X6_UNORM_2PACK16
VK_FORMAT_R10X6G10X6B10X6A10X6_UNORM_4PACK16
VK_FORMAT_G10X6B10X6G10X6R10X6_422_UNORM_4PACK16
VK_FORMAT_B10X6G10X6R10X6G10X6_422_UNORM_4PACK16
VK_FORMAT_R12X4_UNORM_PACK16
VK_FORMAT_R12X4G12X4_UNORM_2PACK16
VK_FORMAT_R12X4G12X4B12X4A12X4_UNORM_4PACK16
VK_FORMAT_G12X4B12X4G12X4R12X4_422_UNORM_4PACK16
VK_FORMAT_B12X4G12X4R12X4G12X4_422_UNORM_4PACK16
VK_FORMAT_G16B16G16R16_422_UNORM
VK_FORMAT_B16G16R16G16_422_UNORM
VK_FORMAT_R16G16_S10_5_NV
```

Start by locating the JSON file that backs the mapping appendix and inspect how existing supported formats record type size and block dimensions. Add entries for the listed formats, then verify that the appendix includes each one with the requested metadata.

Written by the indexing model from the issue text.