fix(web): deploy, deploy revoke and deploy list refusals reach the caller

[cvince]

Seven guards across the three deploy-family classes. All sit inside an execute() whose catch routes to displayErrorAndExit, so each becomes a coded throw and the existing catch serves the page.

class	refusal	code
DeployCommand	authentication failed	AUTH_FAILED
	bad --platform value	INVALID_FORMAT
DeployRevokeCommand	uninitialised project	PROJECT_NOT_INITIALIZED
	authentication failed	AUTH_FAILED
	no token with that prefix	DEPLOY_TOKEN_NOT_FOUND
DeployListCommand	uninitialised project	PROJECT_NOT_INITIALIZED
	authentication failed	AUTH_FAILED

Two deliberately left

Both for the same reason: the message is already on screen before the exit, so converting would print it twice — once by the existing call, once by the error screen.

• mintOrExit — spinner.fail(...) has already rendered the failure
• ambiguous prefix — a multi-line console.error concatenation

Each needs its existing output folded into the throw, which is an edit with a copy decision in it rather than a mechanical one. Same call as the two role-grant refusals left in inviteCommand.

Suite: 1851 pass, 0 fail.