feat(devops): implement group treasury deploy automation

[Depo-dev]

Summary

• Adds contracts/scripts/deploy_group_treasury.sh mirroring the structure of deploy_token_transfer.sh
• Validates all required env vars before doing any network work
• Adds GROUP_TREASURY_CONTRACT_ID to .env.example

Deployment flow

1. Validate env vars (DEPLOYER_SECRET, ADMIN_ADDRESS, TOKEN_CONTRACT_ID, INITIAL_MEMBERS)
2. Validate INITIAL_MEMBERS: parse comma-separated list, reject empty entries
3. Build group_treasury WASM with cargo build
4. Upload WASM to testnet, capture WASM_HASH
5. Deploy contract instance, capture CONTRACT_ID
6. Call initialize with --admin, --token_contract, and --members flags
7. Print contract ID and .env setup instructions

Env var requirements

• DEPLOYER_SECRET: Stellar secret key of the deployer account
• ADMIN_ADDRESS: Stellar public key for the treasury admin
• TOKEN_CONTRACT_ID: Contract ID of the SEP-41 token
• INITIAL_MEMBERS: Comma-separated Stellar public keys (e.g. G...,G...,G...)

Initialization logic

Members are parsed from the comma-separated INITIAL_MEMBERS string and passed as repeated --members flags to the stellar CLI. Whitespace around each address is trimmed.

Output

On success the script prints:

• WASM hash
• Contract ID
• Admin, token, and member summary
• Ready-to-paste .env line: GROUP_TREASURY_CONTRACT_ID=

Validation performed

• bash -n syntax check passes (no errors)
• Script structure reviewed against deploy_token_transfer.sh conventions
• All env guards use set -euo pipefail for immediate failure on any error

Fixes #42

[drips-wave]

@Depo-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[codebestia]

Please resolve the conflicts.

[codebestia]

LGTM!
Thanks