[ET-VK][ez] Add lint rule to check no debug mode in shaders + clean up debug mode usage

[SS-JIA]

Stack from ghstack (oldest at bottom):

• [ET-VK] buffer implementation of rotary positional embeddings #15620
• [ET-VK] Implementation of to_dim_order_copy #15619
• [ET-VK][ez] Fuse update_cache + custom_sdpa into sdpa_with_kv_cache #15618
• [ET-VK] Implement select_at_dim_as_symint #15617
• -> [ET-VK][ez] Add lint rule to check no debug mode in shaders + clean up debug mode usage #15616

Title says it all!

Differential Revision: D86340342

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

✅ You can merge normally! (6 Unrelated Failures)

As of commit d5fee21 with merge base 2b02316 ():

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-openvino-linux / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / test-setup-linux-gcc / linux-job (gh) (trunk failure)
  ##[error]The operation was canceled.
• pull / unittest / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• pull / unittest-editable / windows / windows-job (gh) (trunk failure)
  backends/xnnpack/test/ops/test_conv1d.py::TestConv1d::test_qs8_conv1d_batchnorm_seq
• Test Metal Backend / export-voxtral-metal-artifact / macos-job (gh) (trunk failure)
  /Users/ec2-user/runner/_work/executorch/executorch/pytorch/executorch/pip-out/temp.macosx-11.0-arm64-cpython-311/cmake-out/configurations/optimized_native_cpu_ops_lib/NativeFunctions.h:72:228: error: no template named 'optional' in namespace 'torch::executor'; did you mean 'executorch::aten::optional'?

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.