Alter extension warning for super_user

[amvanbaren]

Fixes #474

Testing Steps

• Publish extension using privileged user:

curl --location --request POST 'http://localhost:8080/api/-/publish?token=super_token' \
--header 'Content-Type: application/octet-stream' \
--data-binary '@<PATH_TO_VSIX>'

• JSON response verified field should be true

[amvanbaren]

@filiptronicek super_token is linked to the super_user, which is an admin user. Should admin users also be considered to be privileged users?

[filiptronicek]

@amvanbaren thanks for that, now it makes sense, didn't spot that there's a difference. I think admin users can be considered privileged users, making extensions from them verified would make sense to me.

[amvanbaren]

thanks for that, now it makes sense, didn't spot that there's a difference.

Me neither. I was a bit too quick to assume the testing steps would just work. The last commit makes an admin a privileged user too.