fix: merging dev changes to main

[Roopan-Microsoft]

Purpose

• This pull request includes minor improvements to deployment documentation and a small update to the broken links checker workflow. The documentation changes clarify deployment instructions and update terminology, while the workflow change simplifies the arguments passed to the broken links checker.

Documentation improvements:

• Updated the heading and section references to clarify that deployment is in "VS Code Dev Containers" instead of just "VS Code". (docs/DeploymentGuide.md)
• Improved instructions for running the sample data script by specifying the use of a Git Bash terminal and clarifying the deployment time estimate. (docs/DeploymentGuide.md)
• Simplified the section on configurable deployment settings by removing the parameter table and improving the reference to customization documentation. (docs/DeploymentGuide.md)

Workflow update:

• Removed the --exclude-mail argument from the lychee-action step in the broken links checker workflow to simplify link checking. (.github/workflows/broken-links-checker.yml) [1] [2]

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• I have built and tested the code locally and in a deployed app
• For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
• This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information