Add --target-path option for local release builds

[Copilot]

This PR adds support for specifying a target directory where local build artifacts will be copied after successful builds. When using the --local flag with alex release start, users can now use the --target-path option to define where build results should end up.

Usage

# Copy build artifacts to ~/releases directory
alex release start --local --target-path ~/releases

# Build only Android and copy to specific directory  
alex release start --local --platforms android --target-path /tmp/android-builds

Implementation

The implementation adds:

• New --target-path (-t) command line argument with proper help documentation
• Enhanced _localBuild method to accept the target path parameter
• New _copyBuildArtifact method that:
  • Parses Flutter build output to extract artifact paths (e.g., .aab, .ipa files)
  • Creates the target directory if it doesn't exist
  • Copies build artifacts to the specified location
  • Provides informative success/error messages

Example Output

Run local build for android
✓ Built build/app/outputs/bundle/release/app-release.aab (27.1MB).
Created target directory: /home/user/releases
Copied android build artifact to: /home/user/releases/app-release.aab

The feature is optional and backward compatible - existing workflows continue to work unchanged when the target path is not specified.

Fixes #37.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

@greymag 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs.

I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review.