fix: pull ssv-dkg v3.1.1 in the ceremony command

The initiator image was pinned to v3.0.3 while the temporary address gate
requires every operator node to run at least 3.1.1, so the generated command
told users to run a client older than the operators it talks to.

Bumping DKG_VERSIONS.NEW covers both call sites: the init command and the
reshare/resign command, which takes the same constant as its default. The
mount-path and log-flag branches compare against the constant rather than a
literal, so they are unaffected. v3.1.1 is published on Docker Hub and is
currently the `latest` tag.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Author: stefan-ssv-labs

src/lib/utils/keyshares.ts

@@ -21,7 +21,10 @@ export enum KeysharesValidationErrors {
 
 export const DKG_VERSIONS = {
   OLD: "2.1.0",
-  NEW: "3.0.3",
+  // Image tag the ceremony command tells the initiator to pull. Kept in step
+  // with MIN_VERSION_FOR_ADDRESS so the initiator never runs an older client
+  // than the operators it is talking to.
+  NEW: "3.1.1",
   // TEMPORARY: an operator's DKG endpoint is only usable once its node runs at
   // least this version. Below it the address must not reach the user or be
   // embedded in a ceremony command. Remove once every operator has upgraded.