Create a command to generate pub/private keypair for pool with the right field name

[janewang]

Today, validators use to near generate-key <pool_id> to create a pub/private key for their

This creates a JSON file containing:

{ "account_id": "account_id", "public_key": "ed25519:HeaBJ3xLgvZacQWmEctTeUqyfSU4SDEnEwckWxd92W2G", "private_key": "ed25519:****" } 

At this point, the validator has to manually change field name “private_key” to “secret_key”, which is suboptimal.

Is your feature request related to a problem? Please describe.
I suggest we create a new command
near generate-pool-key <pool_id> that would create the file:

{ "account_id": "account_id", "public_key": "ed25519:HeaBJ3xLgvZacQWmEctTeUqyfSU4SDEnEwckWxd92W2G", "secret_key": "ed25519:****" } 

Additional context
This is important during validator onboarding to avoid unnecessary and manual key file editing.

[willemneal]

Our of curiosity, why is there a difference in the name of the field? Should we perhaps address this with a better key standard?

(though clearly use this as temporary measure)