docs: added readme for local setup

[AjitPadhi-Microsoft]

Purpose

• This pull request adds a new local development guide to the project documentation. The guide provides step-by-step instructions for setting up the application locally, including environment requirements, configuration, and running the app.

Documentation improvements:

• Added a new LocalSetupGuide.md file with detailed instructions for setting up the development environment, configuring environment variables, using a Python virtual environment, and starting the application locally.

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

• ...

Other Information

[Copilot]

Pull Request Overview

This pull request adds comprehensive local development documentation to help developers set up the application in their local environment. The guide includes prerequisites, step-by-step setup instructions, and configuration details.

Key changes:

• Added a new LocalSetupGuide.md file with detailed local development setup instructions
• Provided clear requirements including Python 3.10+, Azure CLI, and Visual Studio Code
• Included steps for environment configuration, virtual environment setup, and application startup

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The instruction should clarify the exact format for setting APP_ENV. Consider providing the complete line format, e.g., 'APP_ENV=dev' to make it clearer for developers.

Suggested change

	- Make sure to set APP_ENV to "**dev**" in `.env` file.
	- Make sure to set `APP_ENV=dev` in your `.env` file.

[Copilot]

This instruction lacks the specific commands needed to create and activate a virtual environment. Consider adding the actual commands: 'python -m venv venv' and 'source venv/bin/activate' (Linux/Mac) or 'venv\Scripts\activate' (Windows).

Suggested change

	- Navigate to the `src` folder, then create and activate your virtual environment `venv`:
	**Linux/Mac:**
	```bash
	python -m venv venv
	source venv/bin/activate

Windows:

python -m venv venv
venv\Scripts\activate

[Copilot]

The instruction assumes these scripts exist but doesn't specify their location. Consider clarifying where these scripts are located (e.g., 'in the src folder') and what to do if they don't exist.

Suggested change

	- In the `src` folder, run `start.cmd` (Windows) or `start.sh` (Linux/Mac) to:
	- Install backend dependencies.
	- Install frontend dependencies.
	- Build the frontend.
	- Start the backend server.
	> **Note:** If `start.cmd` or `start.sh` do not exist in the `src` folder, ensure you have checked out the correct branch or contact the repository maintainer for assistance.