Add `--package` flag to `stellar contract deploy`

[leighmcculloch]

What problem does your feature solve?

When working in a Cargo workspace, stellar contract deploy will build and deploy all contracts in the workspace. However, there's no way to deploy a subset of packages without either running the command from inside a specific crate's directory or pre-building and passing the WASM path explicitly. stellar contract build already supports a --package flag for selecting specific packages, but deploy does not.

What would you like to see?

Add a --package flag to stellar contract deploy (and stellar contract install), consistent with how stellar contract build already supports --package. This would allow deploying a specific package from a workspace, e.g.:

stellar contract deploy --package my-contract --source alice --network testnet

The flag should behave the same as it does for stellar contract build, selecting a specific package (or subset of packages) within a Cargo workspace to build and deploy.

What alternatives are there?

• cd into the specific crate's directory before running stellar contract deploy
• Run stellar contract build --package my-contract first, then stellar contract deploy --wasm target/... with the explicit WASM path