feat: add NodeId(id) to every log entry for integration-tests

[ChaoticTempest]

Makes debugging what is going wrong with a specific node by introducing the NodeId(id) appended to every logline in integration tests. These will not appear on the actual prod environments.

For example:

NodeId(1) 2025-01-17T21:54:40.653693Z  INFO mpc_node::protocol::consensus: started(initializing): starting key generation as a part of the participant set

[volovyks]

Not sure if it's a good idea ti introduce one more node identifier. We already have accounId and node index from cait-sith library. Should we use one of them instead? Probably accountId, It should be easier to use with tracing since it's available from the start.

[ChaoticTempest]

the issue with using account-ids is that we're creating dev accounts (dev-{long-timestamp}.near). in our integration tests. It's really hard to tell a part which node is which just based on them. The node id is effectively the index from cait-sith as long as there are no weird edge cases when it comes to adding new participants

[volovyks]

Yes, in a cryptographic context, it is. I do not mind using it. I am just not sure if there is a convenient way to set it as a parameter in tracing.

[ChaoticTempest]

Yes, in a cryptographic context, it is. I do not mind using it. I am just not sure if there is a convenient way to set it as a parameter in tracing.

hmm, what do you mean? it already gets set by default with this PR in our integration tests. No need for you to write it manually each time

[volovyks]

I see. I have not noticed it is optional and can be limited in production. Ok.