chore: merge dev into main (features, bug fixes, infra updates)

[Prasanjeet-Microsoft]

Purpose

• This PR merges the latest development work from dev into main. The changes include major enhancements to test automation, infrastructure, naming conventions, CI/CD improvements, and user experience tweaks across the accelerator.

Summary of Changes

1. Test Automation & E2E (End-to-End) Coverage

• Introduced a new folder tests/e2e-test with Playwright + pytest-based automation scripts.
• Added a GitHub Actions workflow (test-automation.yml) to run E2E tests weekly and on pushes to main/dev.
• Supporting files: requirements.txt, pytest.ini, sample .env, and test data for robust testing and documentation.

2. Infrastructure & Naming Consistency

• Added infra/abbreviations.json and updated Bicep/JSON infra templates to use consistent Azure resource abbreviations (e.g., oai- for OpenAI, kv- for Key Vault, etc.).
• Output and parameter naming is now uniform and easier to follow.
• Improved main.bicep with new variables, outputs, and resource naming logic.

3. CI/CD Improvements

• Updated .github/workflows/ci.yml and tests.yml to improve coverage and reliability.
• Made sure tests run from the correct directory and artifacts are always uploaded.

4. Application/UI Improvements

• Backend: Improved error handling (e.g., for invalid URLs in data ingestion).
• Frontend: Enhanced ChatHistoryListItemCell with tooltips, more robust testing, and better accessibility.

5. Documentation

Added/updated README files for new test automation features.
Provided clear instructions for running and customizing tests and infrastructure.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

End-to-End Test Automation

• E2E tests in tests/e2e-test run successfully via the new test-automation.yml workflow (GitHub Actions).
• Test results are uploaded as artifacts and notifications (if configured) are working.
• Local test setup instructions in the new README work as described.

Infrastructure Changes

• Azure resource naming conventions (as per infra/abbreviations.json) are applied consistently across all Bicep/JSON templates.
• Deployments using updated Bicep files (main.bicep, etc.) complete successfully and resources are named as expected.
• All new parameters and outputs are present and correctly documented.

CI/CD Workflows

• CI workflows (ci.yml, tests.yml) run without errors on pushes to main and dev.
• Artifacts (test results, logs) are correctly generated and accessible.

Application/UI Updates

• Backend: Error handling improvements (e.g., invalid URLs in ingestion script) work as expected; app does not crash on bad input.
• Frontend: Tooltips in ChatHistoryListItemCell display correctly and improve accessibility.
• All new/updated tests for UI components pass.

Documentation

• New and updated README files are clear, accurate, and provide complete instructions for test automation and infrastructure deployment.
• Sample .env and test data files are present and usable as per documentation.