Add nexus-proofs as an optional dependency of core

[Marketen]

Adds nexus-proofs.dnp.dappnode.eth 0.1.0 to optionalDependencies, and a nexus_proofs input to the release workflow so its pin is bumped like the other core packages.

How optional dependencies behave

When the dappmanager resolves core, DappGetFetcher.dependencies in the installer package adds an optional dependency to the dependency set only if that package is already installed on the node:

• Nodes without Nexus Proofs: the entry is ignored. Core updates never install it, and bumping its pin does nothing for these nodes.
• Nodes with Nexus Proofs: it is treated as a normal dependency. A core update that bumps the pin updates it.

The ISO installer (dappnode_install.sh) uses a hardcoded package list, so fresh installs do not get Nexus Proofs either.

Things to know

• 0.1.0 is the latest version in the registry and is signed by the dnp key.
• Keep the pin at or above what nodes run. The core resolver refuses to downgrade an installed package. If a node runs a newer Nexus Proofs than core pins, core resolution fails with ErrorDappGetDowngrade and getCoreUpdateData reports no core update for that node. Nexus Proofs is not in the dappmanager's corePackagesNotAutoupdatable, so it can also update on its own (per-package auto-update or the store). Bump this pin whenever Nexus Proofs is released.
• workflow_dispatch now has 10 inputs, which is GitHub's limit. Adding another core package to this workflow will require restructuring it, for example by passing all versions in one JSON input.
• This PR does not bump core's version. The Main workflow does that when it publishes.

🤖 Generated with Claude Code