fix: Changed 'bash' to 'command' in hooks.json

[parveen-dotnet]

As per VS code docs, I don't find "bash" as a property in hooks, the best/suitable property is "command". Reference:
https://code.visualstudio.com/docs/copilot/customization/hooks#_hook-command-properties

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, hooks or workflow with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.

---

Description

Changed 'bash' to 'command' in hooks.json
As per VS code docs, I don't find "bash" as a property in hooks, the best/suitable property is "command". Reference:
https://code.visualstudio.com/docs/copilot/customization/hooks#_hook-command-properties

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• Update to existing instruction, prompt, agent, plugin, skill, hooks or workflow.
• Other (please specify):

---

Additional Notes

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[aaronpowell]

This is, unfortunately, a case where we have deviation between implementations, as Copilot CLI uses a slightly different schema to what VS Code uses.

Before we can action on this PR I'm going to have to work with the teams to get it aligned.

[parveen-dotnet]

Thanks @aaronpowell for the clarification. I wasn't aware of the schema deviation between the Copilot CLI and VS Code implementations. I'll hold off on this change for now until the schemas are aligned. Please let me know once there's an update and I’ll be happy to revisit the PR.

[aaronpowell]

We're actively tracking the changes internally on CLI so hopefully it won't be too long