Verify release signature

[dapplion]

Verify the release signature status following the specs from #891 and dappnode/DAppNode#332

TODO:

• Decide the UX (what to do) when a release is not signed and when it's signed by an unknown key.
  • Packages from IPFS without a valid signature are not allowed to install. However, the restriction can be waved with BYPASS_SIGNED_RESTRICTION option
• Add e2e test uploading a release to IPFS with a signature

Next steps:

• Add support for more signature protocols

Closes #891

---

To test this PR:

1. Install this DAPPMANAGER version
2. Try to install a package from IPFS (not signed) and expect the DAPPMANAGER to block installation (like with the core restriction)
3. Expand extra options and tick the "bypass signed restriction" box. Then the DAPPMANAGER must allow installation
4. Use the UI in this PR Add sign release functionality sdk-publish#3 to sign a release
5. Go to UI > Advanced > Trusted Release Keys and add the address used to sign the release
6. DAPPMANAGER must allow installation of the release and display status that it's signed by that known key

[github-actions]

🚀 Deployed on https://616d96863b396f358ae188e1--objective-borg-9eeae5.netlify.app

[github-actions]

DAppNode bot has built and pinned the release to an IPFS node, for commit: 485c8bf

This is a development version and should only be installed for testing purposes, install link

/ipfs/Qmb2EQrDTiREZSc7E3N9VJWgJMXyKa5XNMMt4Fghv42r72

(by dappnodebot/build-action)

[dapplion]

DAPPMANAGER successfully blocks installation of unsafe packages, but the BYPASS_SIGNED_RESTRICTION does not work. I've tested installing the ssv prater package QmQ4Nv8PE3tfRFVCKosjiyxV5aU4SBp3gviirMaGrBtTjx from IPFS but checking the BYPASS_SIGNED_RESTRICTION box doesn't let you move forward. @pablomendezroyo can you help me investigate?