Does not create "prover-id" file on initial startup if not present, fails when trying to read from missing "prover-id" file.

[Jackalgirl]

Upon initial startup, the code does not generate an initial "prover-id" file. This means that when started, the prover will see that the file does not exist, and instead of creating one, will generate a new prover-id every time. The relevant code seems to be here:

network-api/clients/cli/src/prover_id_manager.rs

Line 21 in e3b2833

// Try to read the prover-id file

The error that's returned on initial startup is:
Could not read prover-id file: No such file or directory (os error 2)
Failed to create .nexus directory: File exists (os error 17)
Connecting to wss://beta.orchestrator.nexus.xyz:443/prove...
Connected.
Your assigned prover identifier is [prover identity].

The manual fix for this is:

1. go to the .nexus directory
2. create a file named prover-id
3. paste in the prover-id that was assigned in the first startup
4. save and exit (default read perms seem to be fine for this for now)
5. restart the prover

It looks like the code will create a .nexus directory if it doesn't exist, but it doesn't create a prover-id file if that file isn't found (around line 35 of the code), which is (I think, I'm not a coder) the issue here.

[collinjackson]

We've made some changes to the code around prover ids on startup. Please check tomorrow's release and let me know if it helps or if this issue remains.