Add projected_enactment_at_start_of_epoch to pending protocol update in health API

[LukasGasior1]

Adds (all optional):

• projected_fulfillment_at_start_of_epoch and projected_fulfillment_timestamp for each threshold of a pending protocol update
• projected_enactment_at_start_of_epoch and projected_enactment_timestamp to a pending protocol update, which are the values of the threshold which is projected to fulfill earliest

Notes:

• if the threshold is not met then its values are null
• if projected epoch is out of min/max bounds then the result is also null

[github-actions[bot]]

Docker tags docker.io/radixdlt/private-babylon-node:pr-862 docker.io/radixdlt/private-babylon-node:cdd12fcde0 docker.io/radixdlt/private-babylon-node:sha-cdd12fc

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
63.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud[bot]]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
59.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud