Use local Hex key to revoke local Hex API key

[scristobal]

resolves #4319

After a bit of though, I realized we can use the existing key to revoke itself. Provided the Hex API allows such a thing.

As it turns out, using the existing key to revoke itself works just fine, but requires asking the user for the local password. Hence the command flow needs to change a bit. Here is the result:

In any case, if the key couldn't be revoked, the user is hinted to finish the process manually, instead of failing, like in #4319.

Please do let me know if you think this approach is a good fit.

Thanks!

[lpil]

Thank you!

Rather than decrypting it first we should only do it if the new key cannot be used to delete the old one. The most common reason to overwrite the existing key is if the programmer has forgotten their password, as it's very rare for someone to have multiple Hex accounts. There's not really any reason to make more than one because Hex supports organisations and multiple maintainers per package.

[scristobal]

Thank you!

Rather than decrypting it first we should only do it if the new key cannot be used to delete the old one. The most common reason to overwrite the existing key is if the programmer has forgotten their password, as it's very rare for someone to have multiple Hex accounts. There's not really any reason to make more than one because Hex supports organisations and multiple maintainers per package.

uuups, it makes sense. I will put this is in draft mode and come back later.

[scristobal]

follow up in #4446