feat: Add support in App Automate for Appium

[tech-sushant]

No description provided.

[Copilot]

Pull Request Overview

This PR adds comprehensive support for Appium-based testing in the App Automate tool. It restructures the codebase to separate native execution (Espresso/XCUITest) from Appium SDK integration, enabling users to set up BrowserStack App Automate with Appium across multiple programming languages and testing frameworks.

Key Changes

• Restructures App Automate utilities into native-execution and appium-sdk modules
• Adds new setupBrowserStackAppAutomateTests tool for Appium SDK integration
• Implements multi-language support for Appium (Java, C#, Python, Node.js, Ruby)

Reviewed Changes

Copilot reviewed 19 out of 19 changed files in this pull request and generated 4 comments.

File	Description
src/tools/appautomate.ts	Adds new setupBrowserStackAppAutomateTests tool and reorganizes imports
src/tools/appautomate-utils/native-execution/types.ts	Moves and updates type definitions, removes APPIUM enum value
src/tools/appautomate-utils/appium-sdk/	New module with comprehensive Appium SDK setup utilities
tests/tools/appautomate.test.ts	Updates import path to match new structure

---

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

[Copilot]

The Maven command construction uses template literals that reference process.env variables, but these will be evaluated at build time rather than runtime. This will likely result in 'undefined' values being inserted into the command string. The variables should be passed as parameters or handled differently.

[Copilot]

Same issue as in getMavenCommandForWindows - the process.env references will be evaluated at build time, not runtime, likely resulting in 'undefined' values in the Maven command.