Feat/ansible deployment tags

[vivekgsharma]

Added tags to deploy.yml to better structure and allow selective execution of tasks. This improves maintainability and provides flexibility when running the playbook.

Issue being fixed or feature implemented

Added tags to deploy.yml to better structure and allow selective execution of tasks. This improves maintainability and provides flexibility when running the playbook.

What was done?

• Introduced full_deploy tag for executing the entire playbook at once.
• Added categorized tags for better task selection:
  • Infrastructure setup (docker, AWS, Python, etc) (infra_setup)
  • Masternode updates (update_masternodes)
  • HP Masternode updates (update_hp_masternodes)
  • Masternode unbanning (unban_masternodes)
  • HP Masternode unbanning (unban_hp_masternodes)
  • Core updates (core_update)
  • Platform updates (platform_update)
  • Monitoring & Logging (monitoring, logging)
  • Tenderdash update (update_seed_nodes)
  • Cleanup (cleanup)

How Has This Been Tested?

Enter any of the above tags to selectively deploy parts of the playbook.
Below are some example executions that were tested:

./bin/deploy -p testnet --tags=unban_masternodes,unban_hp_masternodes
./bin/deploy -p testnet --tags=unban_masternodes
./bin/deploy -p testnet # Deploys the full playbook (default behavior)

Breaking Changes

No breaking changes. It has been tested from the deployment server.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[ktechmidas]

No need to do this more than once, maybe once in a blue moon when Pasta requires it... leave it as just full_deploy for now