refactor: Admin UI Trigger Deploy uses LagoonClientService directly (not Artisan CLI wrapper)

[Copilot]

The Trigger Deploy admin action was calling the polydock:app-instance:trigger-deploy Artisan command via Artisan::call(), obscuring that the mechanism is the Lagoon API — not the CLI. Both the deployment action and the deployment info form section now call LagoonClientService directly.

Changes

ViewPolydockAppInstance.php

• Action: Replaced Artisan::call('polydock:app-instance:trigger-deploy', ...) with a direct LagoonClientService::getAuthenticatedClient() + deployProjectEnvironmentByName() call
• Form: Replaced duplicated inline SSH/config setup with LagoonClientService::getLagoonToken() (cached) + buildClientWithToken() — same caching behaviour, no more duplicated config wiring
• Separate, specific error messages for missing project name vs. missing branch
• Removed unused imports: Artisan, Client, Ssh

LagoonClientService.php

• getLagoonToken() promoted from protected to public with an optional $config param (defaults to getClientConfig()) — enables external token caching
• New buildClientWithToken(array $config, string $token): Client — constructs a configured client from a pre-fetched token; getAuthenticatedClient() now delegates to it

// Before: opaque Artisan indirection
Artisan::call('polydock:app-instance:trigger-deploy', [
    'instance_uuid' => $instanceUuid,
    '--environment' => $environment,
    '--force' => true,
]);

// After: explicit API call via LagoonClientService
$client = app(LagoonClientService::class)->getAuthenticatedClient();
$result = $client->deployProjectEnvironmentByName(
    projectName: $projectName,
    deployBranch: $environment,
);

---

💡 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.