Issue teamplate for JS automation tools

Please describe an issue in JS automation tools area and which could help understand more context when fixing or review the pr.

------------------------------------
## Affected Component
Which part of the automation tool is impacted?

e.g., Generation, Publish Sample, Bump Version, Breaking Detection etc.

## Bug Description
What is the issue? Describe the behavior clearly.

Include error messages, logs, or screenshots if applicable.

## Impact Scope
How widespread is the issue?

e.g., Affects all SDKs, only specific platforms, or a corner case.

## Expected Behavior
What should happen instead?

Describe the correct or intended behavior.

## Workaround Attempted (Optional)
Have you tried any temporary fixes? Do we have any workaround?

e.g., Manual patching, skipping steps, using older versions.

6. Root Cause Analysis (Optional)
If known, what caused the issue?

e.g., Regression from recent commit, dependency conflict.

## Additional Context (Optional)
Any other relevant information?

e.g., Links to related issues, ci links, or documentation.

Would you like this turned into a markdown file or integrated into a GitHub issue template format (.github/ISSUE_TEMPLATE/bug_report.md)?

Review the requested issue-template content and compare the repository's existing .github/ISSUE_TEMPLATE/bug_report.md, if present. Confirm whether the deliverable is a standalone Markdown file or a GitHub issue-template integration, then ensure the chosen template captures the affected component, bug description, impact, expected behavior, workaround, root cause, and additional context.

Written by the indexing model from the issue text.