Documentation: README Enhancements (#62)

* Documentation: README Enhancements, Repo Polish & Zero-Allocation Optimizations (#51)

This PR implements comprehensive documentation and repository enhancements as specified in issue #51. It also includes critical performance optimizations to achieve zero-allocation happy-path execution for Resilience Policies.

- **README Enhancements**: Added Mermaid diagrams for thundering herd vs. jittered retries and request lifecycle. Refactored use cases into a 'Resilience Cookbook'. Added 'Aha!' snippet and hyperscaler research branding.
- **Performance**: Achieved 0 B/op and 0 allocs/op on the happy path for pre-configured Policies. Added benchmark_test.go to verify and showcase these results.
- **Optimizations**: Implemented middleware pipeline caching and stateless execution paths to eliminate heap allocations during execution.
- **Issue Templates**: Enhanced bug report and feature request templates with structured sections.
- **Community**: Created 'good first issue' tickets for new database and cache examples.

fixes #51

* Docs: Refine README, enhance issue templates, and add benchmarks (#51)

* Docs: Restore full license section in README.md

Author: cinar

.github/ISSUE_TEMPLATE/bug_report.md

@@ -10,22 +10,23 @@ assignees: ''
 **Describe the bug**
 A clear and concise description of what the bug is.
 
+**Environment**
+- Resile Version: [e.g. v1.0.0]
+- Go Version: [e.g. 1.22]
+- OS/Arch: [e.g. Linux/amd64]
+
 **To Reproduce**
-Steps to reproduce the behavior:
-1. ...
-2. ...
-3. ...
+Steps to reproduce the behavior. A minimal, self-contained Go program is highly preferred.
+
+```go
+// Paste your minimal reproduction code here
+```
 
 **Expected behavior**
 A clear and concise description of what you expected to happen.
 
-**Code Snippet**
-If possible, please include a minimal code example to reproduce the issue.
-
-**Context**
-- Go version: [e.g. 1.22]
-- Resile version: [e.g. v1.0.0]
-- OS: [e.g. Linux, macOS]
+**Actual Behavior / Log Output**
+If applicable, add logs or error messages to help explain your problem.
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -10,8 +10,11 @@ assignees: ''
 **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 [...]
 
-**Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+**The "Aha!" Use Case**
+Describe the real-world scenario where this feature would be most useful.
+
+**Proposed Implementation**
+A clear and concise description of how you'd like the feature to be implemented. If possible, provide a code snippet of how the API should look.
 
 **Describe alternatives you've considered**
 A clear and concise description of any alternative solutions or features you've considered.