feat: implement complete tree-sitter-shellspec grammar with comprehensive testing

- Add full ShellSpec grammar extending tree-sitter-bash
- Support all ShellSpec constructs: Describe, Context, It, hooks, utilities
- Include Data block parsing with statements and argument styles
- Add 61 comprehensive test cases covering real-world patterns
- Implement optimized GitHub workflows with CI/CD automation
- Configure complete development tooling (linting, formatting, pre-commit)
- Add comprehensive documentation and contribution guidelines
- Optimize grammar conflicts to zero warnings
- Support editor integration for Neovim, VS Code, Emacs

Breaking Changes:
- Initial release, no previous API to break

BREAKING CHANGE: Initial implementation of tree-sitter-shellspec grammar

# Conflicts:
#	.github/workflows/codeql.yml
#	.github/workflows/pr-lint.yml
#	.pre-commit-config.yaml

# Conflicts:
#	.github/workflows/pr-lint.yml

# Conflicts:
#	.github/workflows/pr-lint.yml

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,32 @@
 ---
 name: Feature request
-about: Suggest an idea for this project
-title: ''
+about: Suggest a grammar enhancement or new feature for tree-sitter-shellspec
+title: "[FEATURE] "
 labels: enhancement
 assignees: ivuorinen
-
 ---
 
-**Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+**Is your feature request related to a ShellSpec parsing issue?**
+A clear description of what ShellSpec syntax is not currently supported. Ex. "Data blocks with :expand modifier are not parsed correctly"
+
+**ShellSpec syntax example**
+Please provide an example of the ShellSpec syntax you'd like to see supported:
+
+```shellspec
+# Example ShellSpec code that should be supported
+```
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+A clear description of how this syntax should be parsed or highlighted.
 
-**Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+**Current behavior**
+How does the parser currently handle this syntax? (if at all)
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+**Use case**
+Why is this syntax important? How commonly is it used in ShellSpec tests?
+
+## Additional context
+
+- Link to ShellSpec documentation for this feature (if available)
+- Examples from real-world ShellSpec test suites
+- Any other context or screenshots about the feature request