Remove the license from the site even when deactivation fails

[jakejackson1]

Reverts the "keep the license key on screen and allow another attempt" behaviour from #1682. A failed deactivation now still removes the key from the site.

Why

Helper_Abstract_Addon::deactivate_license() deletes the local license info before it inspects the API response:

/* Remove license data from database, no matter if the API request fails */
$this->delete_license_info();
$this->flush_update_cache();

So the key is gone from this site whether or not GravityPDF.com accepted the deactivation. The UI didn't match: on an {error} response or a transport failure it kept the key in the field and left the Deactivate button in place, implying the license was still installed and retryable — but a reload showed an empty field, because the DB row had already been deleted.

What changed

All three outcomes now clear the key/message/status inputs and drop the Deactivate button. Only the message differs:

Response	Fields cleared	Button removed	Message
{success}	✅	✅	green, from server
{error} (API rejected)	✅	✅	red, from server
jqXHR (500 / 401)	✅	✅	red, GFPDF.licenseDeactivationError

The extra teardown for All Access Pass siblings still runs on success only — process_license_deactivation() only populates that list once the API confirms deactivation.

licenseDeactivationError is reworded to match the two equivalent PHP messages in process_license_deactivation(): the user is pointed at their GravityPDF.com account to confirm the site was unlinked, rather than told to reload and retry.

Kept from #1682: the red-vs-green styling fix (genuine {error} responses were previously given the success class) and the repeat-click guard.

Note

On a 401/nonce failure the server never reaches deactivate_license(), so the key is still in the DB and reappears on reload — the UI clears optimistically there. That's the trade-off for "remove it regardless"; the error message points the user at their account to confirm.

Testing

npx jest — 58 suites / 468 tests passing. The three deactivation-path tests were updated to assert the new behaviour; eslint clean.

No changelog entry (per request).

🤖 Generated with Claude Code