fix: Use YAML !env function in Sentry config examples (#1793)

* fix: Use YAML !env function instead of shell-style variable expansion in Sentry config examples

Replace shell-style variable expansion (${VAR}) with proper YAML function
syntax (!env VAR) in all Sentry configuration examples.

Changes:
- Updated website/docs/cli/configuration/errors.mdx
- Updated website/blog/2025-11-08-helpful-errors.mdx

Examples now correctly show:
  dsn: !env ATMOS_SENTRY_DSN
  environment: !env ATMOS_ENV

Instead of:
  dsn: "${ATMOS_SENTRY_DSN}"
  environment: "${ATMOS_ENV}"

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* docs: Remove redundant "Why This Matters" and "What's Next" sections from blog post

Removed two sections that were redundant or not needed:
- "Why This Matters" section
- "What's Next" section

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

* docs: Remove "Real-World Impact" section from blog post

Removed the entire "Real-World Impact" section including:
- "Faster Troubleshooting" subsection with time-to-resolution claims
- "Enterprise Visibility" subsection
- "Better Developer Experience" subsection

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

---------

Co-authored-by: Claude (via Conductor) <[email protected]>
Co-authored-by: Claude <[email protected]>
Co-authored-by: Andriy Knysh <[email protected]>

Author: 4 people

website/blog/2025-11-08-helpful-errors.mdx

@@ -155,63 +155,6 @@ Benefits:
 - **Type-safe** - Static error definitions prevent typos
 - **Testable** - Mock and verify error messages in tests
 
-## Real-World Impact
-
-### Faster Troubleshooting
-
-**Before:**
-```
-Error: command execution failed
-Exit code: 1
-```
-Time to resolution: 30+ minutes (searching docs, trial and error)
-
-**After:**
-```
-# Workflow Error
-
-**Error:** workflow step execution failed
-
-## Explanation
-
-The following command failed to execute:
-atmos terraform plan vpc -s prod
-
-## Hints
-
-💡 To resume the workflow from this step, run:
-   atmos workflow deploy -f prod --from-step deploy-vpc
-
-💡 Check component configuration in stacks/prod.yaml
-
-## Context
-
-• Workflow: deploy
-• Step: deploy-vpc
-• Component: vpc
-• Stack: prod-us-east-1
-• Exit Code: 1
-```
-Time to resolution: 2-3 minutes (clear guidance + exact command to retry)
-
-### Enterprise Visibility
-
-Platform teams can now:
-
-1. **Track error patterns** - "70% of errors are missing AWS credentials"
-2. **Identify problem areas** - "Component X fails validation in 3 different stacks"
-3. **Measure improvement** - "Error rate decreased 40% after documentation update"
-4. **Support teams proactively** - "Team Y has 10x more errors than average"
-
-### Better Developer Experience
-
-Contributors can:
-
-1. **Add helpful errors easily** - Use error builder pattern
-2. **Test error messages** - Verify hints and formatting
-3. **Maintain consistency** - All errors follow the same pattern
-4. **Iterate quickly** - Update hints without changing error handling
-
 ## Configuration
 
 ### Basic Setup (Better Error Messages)
@@ -231,8 +174,8 @@ errors:
   # Sentry integration
   sentry:
     enabled: true
-    dsn: "${ATMOS_SENTRY_DSN}"
-    environment: "${ATMOS_ENV}"
+    dsn: !env ATMOS_SENTRY_DSN
+    environment: !env ATMOS_ENV
 
     # Sample rate: 1.0 = 100%, 0.5 = 50% (default: 1.0)
     sample_rate: 1.0
@@ -282,26 +225,6 @@ return errUtils.Build(errUtils.ErrWorkflowNotFound).
 
 See `docs/errors.md` for the complete developer guide.
 
-## Why This Matters
-
-Infrastructure as Code is complex. When managing hundreds of components across multiple environments, every minute spent debugging is time not spent delivering value.
-
-By providing **helpful hints**, **rich context**, and **enterprise error tracking**, we're:
-
-1. **Reducing time to resolution** - Fix issues in minutes instead of hours
-2. **Improving team productivity** - Less context switching, more building
-3. **Enabling data-driven improvements** - Track and fix systemic issues
-4. **Creating better software** - Consistent, helpful error messages across Atmos
-
-This is infrastructure we wish we'd had years ago. Now it's built into Atmos by default.
-
-## What's Next
-
-We're continuing to improve error handling:
-
-- **More helpful hints** - Adding guidance to more errors across Atmos
-- **Enhanced context** - Automatically include more relevant information with each error
-
 ## Get Involved
 
 We'd love your feedback:

website/docs/cli/configuration/errors.mdx

@@ -200,11 +200,11 @@ errors:
 
     # Use environment variable for dynamic environment name
     # Set ATMOS_ENVIRONMENT in your CI/CD pipeline
-    environment: "${ATMOS_ENVIRONMENT}"
+    environment: !env ATMOS_ENVIRONMENT
 
     # Set release from CI/CD pipeline
     # Example: "v1.2.3" or "commit-abc123"
-    release: "${CI_COMMIT_TAG}"
+    release: !env CI_COMMIT_TAG
 
     # Reduce noise in development
     sample_rate: 0.1  # Only 10% of errors in dev
@@ -256,7 +256,7 @@ export ATMOS_SENTRY_DSN="https://[email protected]/project-id"
 errors:
   sentry:
     enabled: true
-    dsn: "${ATMOS_SENTRY_DSN}"
+    dsn: !env ATMOS_SENTRY_DSN
     environment: "production"
 ```
 </File>
@@ -272,11 +272,11 @@ Track infrastructure deployment failures across all your CI pipelines:
 errors:
   sentry:
     enabled: true
-    dsn: "${SENTRY_DSN}"
+    dsn: !env SENTRY_DSN
     environment: "ci"
     tags:
-      pipeline: "${CI_PIPELINE_ID}"
-      branch: "${CI_COMMIT_BRANCH}"
+      pipeline: !env CI_PIPELINE_ID
+      branch: !env CI_COMMIT_BRANCH
       team: "platform"
 ```
 </File>
@@ -296,12 +296,12 @@ Different teams can share the same Sentry project with custom tags:
 errors:
   sentry:
     enabled: true
-    dsn: "${SENTRY_DSN}"
-    environment: "${ENVIRONMENT}"
+    dsn: !env SENTRY_DSN
+    environment: !env ENVIRONMENT
     tags:
-      team: "${TEAM_NAME}"        # "platform", "security", "data"
+      team: !env TEAM_NAME        # "platform", "security", "data"
       service: "atmos"
-      region: "${AWS_REGION}"
+      region: !env AWS_REGION
 ```
 </File>
 
@@ -321,16 +321,16 @@ Reduce noise in development while maintaining full monitoring in production:
 errors:
   format:
     # More detail in development
-    verbose: ${DEVELOPMENT:-false}
+    verbose: !env DEVELOPMENT false
 
   sentry:
     # Only enable in production/staging
-    enabled: ${SENTRY_ENABLED:-false}
-    dsn: "${SENTRY_DSN}"
-    environment: "${ENVIRONMENT:-development}"
+    enabled: !env SENTRY_ENABLED false
+    dsn: !env SENTRY_DSN
+    environment: !env ENVIRONMENT development
 
     # Sample aggressively in dev, fully in prod
-    sample_rate: ${SENTRY_SAMPLE_RATE:-0.1}
+    sample_rate: !env SENTRY_SAMPLE_RATE 0.1
 ```
 </File>