See https://developer.chrome.com/blog/new-in-webgpu-121#default_entry_points_to_shader_modules for change description.

Acceptance criteria

• Add notes saying that you can omit the entryPoint property in your fragment and vertex shader definitions (see https://developer.mozilla.org/en-US/docs/Web/API/GPUDevice/createRenderPipeline) and your compute shader definitions (see https://developer.mozilla.org/en-US/docs/Web/API/GPUDevice/createComputePipeline) if a unique entry point is defined in the relevant shader code.
• Add descriptions to the Validation sections of the above pages stating that If the entryPoint property is omitted in the case of any of the shader definition objects, and no unique entry point for the shader stage is found in the shader code, a GPUValidationError will be triggered.
• Add a BCD data point for this change (to createRenderPipeline(), createRenderPipelineAsync(), createComputePipeline(), and createComputePipelineAsync()) — this shipped in Chrome 121.