[Merged by Bors] - GRPC service to retrieve state of post proving

[poszu]

Description

Added a new GRPC service that provides a way to get the state of POST proving for all registered identities.

Each identity starts as Idle and transitions to Proving when POST proving phase starts (when the post-service becomes required). This informs the operator that it is time to switch the post-service ON.
The state transitions back to Idle in one of two conditions:

• post proving completed successfully,
• we selected a new nipost challenge. In this situation, the node will need to re-register in poet and will not need to prove until it gets a new poet proof (i.e. for ~2 weeks).

The state does NOT transition from Proving to Idle when post proving fails because it might retry (and hence need the post-service again) and we don't want to confuse the operator with multiple state switches.

Test Plan

Added unit tests

TODO

• Explain motivation or link existing issue(s)
• Test changes and document test plan
• Update documentation as needed
• Update changelog as needed

[codecov]

Codecov Report

Attention: Patch coverage is 90.54054% with 7 lines in your changes are missing coverage. Please review.

Project coverage is 79.7%. Comparing base (3e59df3) to head (32bce25).
Report is 3 commits behind head on develop.

Files	Patch %	Lines
api/grpcserver/post_info_service.go	80.0%	4 Missing ⚠️
common/types/post.go	75.0%	2 Missing ⚠️
node/node.go	83.3%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #5651    +/-   ##
========================================
  Coverage     79.7%   79.7%            
========================================
  Files          274     279     +5     
  Lines        27883   28259   +376     
========================================
+ Hits         22228   22550   +322     
- Misses        4108    4145    +37     
- Partials      1547    1564    +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[fasmat]

Would it make sense to pass postStates here instead of app.atxBuilder?

[poszu]

Yes, but it would require making more code use the types.IdentityDescriptor because the PostInfoService needs to map types.IdentityDescriptor -> types.PostState (not types.NodeID). I think about changing Nipostbuilder::Proof to use it (instead of NodeID) so that it can log the name too in post service not connected - waiting for reconnection {"service id": "5ea2c9975a185eeaa40bc9351297aa98c85952553f0fde4707ad783943c65e2e", "error": "post service not registered"} in a follow up.

[poszu]

bors merge

[spacemesh-bors]

Build failed:

• ci-status

[poszu]

bors merge

[poszu]

bors cancel

[spacemesh-bors]

Canceled.

[poszu]

bors merge

[spacemesh-bors]

Pull request successfully merged into develop.

Build succeeded:

• ci-status
• systest-status