fix: use deployment resource for platform commands

[lusu007]

Pull Request

Description

Fixes platform command polling for multi-flavor Minecraft workloads by separating the logical app name from the deployment resource name used by Forge's deployment-scoped service-account token.

The plugin now resolves the command deployment identity from GROUNDS_RESOURCE_NAME, falls back to the Kubernetes Deployment name derived from HOSTNAME, and finally falls back to GROUNDS_APP_NAME for older or local environments. Command lease and result callbacks use that deployment identity, while existing app-scoped behavior keeps the logical app name.

Type of Change

• 🐛 Bug fix
• ✨ New feature
• 💥 Breaking change
• ♻️ Refactoring
• 📚 Documentation
• 🔧 Chore

Related Issues

• Fixes platform command execution for multi-flavor plugin-paper deployments

Testing

• Unit tests pass
• Manual testing completed
• New tests added for new functionality

Commands run:

• ./gradlew :common:test --tests 'gg.grounds.platform.PlatformEnvTest' --tests 'gg.grounds.platform.commands.PlatformCommandEnvTest' --tests 'gg.grounds.platform.commands.PlatformCommandClientTest'
• ./gradlew test
• ./gradlew spotlessApply
• ./gradlew build

Checklist

• I have performed a self-review of my own code
• Tests have been added/updated and pass (if needed)
• Documentation has been updated (if needed)