Kubernetes VSCode extension resource schema validation

**Describe the problem/challenge you have**
Working with comments has its drawbacks. The [Kubernetes extension](https://github.com/Azure/vscode-kubernetes-tools) for vscode marks all YAML values with only `#@` as invalid.


> Incorrect type. Expected "integer".yaml-schema: kubernetes://schema/apps/v1%40deployment

**Describe the solution you'd like**

- Ship a custom vscode extension
- Improve [Kubernetes extension](https://github.com/Azure/vscode-kubernetes-tools) to understand ytt comments.

---
Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

Start by reproducing the Kubernetes VSCode extension's YAML schema validation with ytt comments using the linked example. Compare the behavior of the existing Kubernetes extension with the proposed custom-extension or improved-extension approaches. Done means values marked with only #@ are no longer reported as invalid by the VSCode validation workflow.

Written by the indexing model from the issue text.