Add region-based PMA endpoints and call transfer functionality

[v-vkaluri]

• Add PMA endpoints for Arizona and Texas regions in app settings
• Implement dynamic endpoint selection based on config boolean in app settings
• Create setRegion endpoint to update PMA endpoint and reinitialize call automation client
• Add call transfer capability for ACS participants

Purpose

• This pull request adds multi-region support for PMA endpoints, specifically for Arizona and Texas regions. It implements dynamic endpoint selection based on configuration settings and adds the ability to transfer calls for ACS participants. These changes enhance the application's flexibility by allowing region-specific configurations and improving call handling capabilities.

Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

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

• Test the code

1. Verify Arizona and Texas PMA endpoints are available in app settings
2. Test dynamic endpoint selection by toggling the config boolean
3. Test the setRegion endpoint functionality
4. Verify call transfer works correctly for ACS participants

What to Check

Verify that the following are valid

• PMA endpoints for Arizona and Texas are correctly implemented and accessible
• The application correctly switches between endpoints based on the configuration setting
• The setRegion endpoint properly updates the PMA endpoint and reinitializes the call automation client
• Call transfers work as expected for ACS participants

Other Information

[v-vkaluri]

@microsoft-github-policy-service agree company="Microsoft"