Add SUPPORT.md file with bug report guidance

[Copilot]

• Explore repository structure and understand codebase
• Verify build and test processes work correctly
• Analyze existing documentation style and format
• Create support.md file with guidance for bug reports
• Ensure support.md follows project documentation style
• Verify content matches issue requirements
• Test final implementation
• Remove package-lock.json changes from changeset as requested

Summary:
Created a comprehensive SUPPORT.md file that provides clear guidance on how to get support by creating well-documented bug reports in GitHub Issues. Removed the unintentional package-lock.json changes from the changeset as requested by @rajbos.

The file includes:

• Clear direction to use GitHub Issues for support
• Detailed guidance on what information to include in bug reports
• Reference to known limitations from the README
• Information about feature requests and contributing
• Follows the same markdown style as other documentation files in the project

The build and lint processes continue to work correctly after all changes.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Create support file</issue_title>
<issue_description>Add a support.md file that indicate the way to get some support is by adding a well documented bug report in an issue</issue_description>

Comments on the Issue (you are @copilot in this section)

Fixes #3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[rajbos]

@copilot remove the package lock file from the cangeset

[Copilot]

@copilot remove the package lock file from the cangeset

Removed package-lock.json changes from the changeset. The file has been reverted to its original state before my changes and the build continues to work correctly.