Nodes generate Secret ID and used retrieving allocations/registering

[dadgar]

Also fixes client tests
@diptanu for review

[diptanu]

Handle the in-place upgrade path.

[diptanu]

I think the right behavior would be - When a node registers and doesn’t provide a secret id, the server returns one if the node was previously registered and didn't have a secret id. The client should never generate a secret id, if it has a secret id and if that doesn’t match with what server has, the server can reject the registration. The client should just store whatever the server is sending in the state file and if an operator has tempered it, next time the node won't get registered until the state file is removed.

[dadgar]

Talked offline with Diptanu

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.