chore: clean up issue templates (#1930)

<!-- ELLIPSIS_HIDDEN -->



> [!IMPORTANT]
> Cleaned up issue templates and replaced YAML-based pull request
template with a Markdown version for better clarity and consistency.
> 
>   - **Issue Templates**:
> - Renamed "BoundaryML" to "Boundary" in `01-bug_report.yml` and
`02-feature_request.yml`.
> - Changed label "To reproduce" to "Reproduction Steps" and "Version"
to "BAML Version" in `01-bug_report.yml`.
> - Removed unnecessary fields in `03-documentation.yml` and made some
fields optional.
>   - **Pull Request Template**:
> - Replaced YAML-based `pull_request_template.yml` with Markdown-based
`pull_request_template.md`.
> - The new template includes sections for issue reference, changes,
testing, screenshots, checklist, and additional notes.
> 
> <sup>This description was created by </sup>[<img alt="Ellipsis"
src="https://img.shields.io/badge/Ellipsis-blue?color=175173">](https://www.ellipsis.dev?ref=BoundaryML%2Fbaml&utm_source=github&utm_medium=referral)<sup>
for 344f9df. You can
[customize](https://app.ellipsis.dev/BoundaryML/settings/summaries) this
summary. It will automatically update as commits are pushed.</sup>

<!-- ELLIPSIS_HIDDEN -->

Author: seawatts

.github/ISSUE_TEMPLATE/01-bug_report.yml

@@ -6,7 +6,7 @@ body:
   - type: dropdown
     attributes:
       label: Product
-      description: Which BoundaryML product are you using?
+      description: Which Boundary product are you using?
       options:
         - BAML
         - VS Code Playground
@@ -23,13 +23,13 @@ body:
       required: true
   - type: textarea
     attributes:
-      label: To reproduce
+      label: Reproduction Steps
       description: Describe how to reproduce your bug. Steps, code snippets, reproduction repos etc.
     validations:
       required: true
   - type: input
     attributes:
-      label: Version (Optional)
+      label: BAML Version (Optional)
       description: Which version of BAML are you using?
   - type: dropdown
     attributes:

.github/ISSUE_TEMPLATE/02-feature_request.yml

@@ -6,7 +6,7 @@ body:
   - type: dropdown
     attributes:
       label: Product
-      description: Which BoundaryML product would this feature be for?
+      description: Which Boundary product would this feature be for?
       options:
         - BAML
         - VS Code Playground

.github/ISSUE_TEMPLATE/03-documentation.yml

@@ -3,42 +3,24 @@ description: Request documentation improvements or report documentation issues
 title: "[docs] "
 labels: ["documentation"]
 body:
-  - type: textarea
-    attributes:
-      label: Documentation Issue
-      description: What documentation needs to be improved or added?
-    validations:
-      required: true
-  - type: textarea
-    attributes:
-      label: Current Documentation
-      description: If applicable, what is the current documentation that needs improvement?
   - type: textarea
     attributes:
       label: Proposed Changes
       description: What changes would you like to see in the documentation?
     validations:
       required: true
-  - type: dropdown
+  - type: textarea
     attributes:
-      label: Product
-      description: Which BoundaryML product's documentation needs improvement?
-      options:
-        - BAML Language
-        - VS Code Playground
-        - Boundary Studio
-        - Prompt Fiddle
-        - Other
+      label: Current Documentation (Optional)
+      description: If applicable, what is the current documentation that needs improvement?
   - type: dropdown
     attributes:
-      label: Documentation Type
+      label: Documentation Type (Optional)
       description: What type of documentation is this?
       options:
         - Getting Started Guide
         - API Reference
         - Tutorial
         - Example
         - Best Practices
-        - Other
-    validations:
-      required: true
+        - Other

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,39 @@
+# Pull Request Template
+
+Thanks for taking the time to fill out this pull request!
+
+## Issue Reference
+Please link to any related issues
+- [ ] This PR fixes/closes #[issue number]
+
+## Changes
+Please describe the changes proposed in this pull request
+
+[Describe your changes here...]
+
+## Testing
+Please describe how you tested these changes
+
+- [ ] Unit tests added/updated
+- [ ] Manual testing performed
+- [ ] Tested in [environment]
+
+## Screenshots
+If applicable, add screenshots to help explain your changes
+
+[Add screenshots here...]
+
+## PR Checklist
+Please ensure you've completed these items
+
+- [ ] I have read and followed the contributing guidelines
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+
+## Additional Notes
+Add any other context about the PR here
+
+[Add any additional notes here...]