#2 feat: Update environment configuration and setup scripts for impro…

[mauricio-morales]

…ved local development

Description

What changed?

Why?

Related Issue(s)

Closes #

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test addition or improvement
• Build/CI configuration change

Testing

How Has This Been Tested?

Test Configuration:

• OS:
• .NET SDK:
• Node.js:
• Browser (if applicable):

Test Steps

Expected Results

Screenshots (if applicable)

Checklist

Code Quality

• My code follows the project's code style guidelines
• I have run dotnet format (backend) or pnpm format (frontend)
• I have performed a self-review of my own code
• My code builds without warnings (dotnet build -c Release or pnpm build)
• I have commented my code, particularly in hard-to-understand areas

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally (dotnet test or pnpm test)
• I have tested the changes in multiple run modes (local, backend, full)

Documentation

• I have updated the documentation (README, inline docs, etc.)
• I have updated the CHANGELOG.md (if applicable)
• My changes generate no new warnings or errors in logs

Dependencies

• I have added/updated NuGet packages using central package management
• I have run pnpm install and committed any lockfile changes
• I have verified no unused dependencies were added

Commit Standards

• My commits follow the Conventional Commits specification
• My commit messages clearly describe what and why (not just how)
• I have rebased my branch on the latest main

Breaking Changes

Additional Notes

---

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.