Remove blazar_upgrade_step metric and add validator_address, chain_id labels to blazar_blocks_to_upgrade_height

[sin3point14]

The blazar_upgrade_step metric isn't human friendly since it exports upgraded step as an integer, one needs to lookup the proto to understand what the integers mean. Hence this PR removes that metric and instead adds upgrade_state and upgade_step as labels to the blazar_blocks_to_upgrade_height metric.

This also adds a validator_address label which is set to .valdiator_info.address from the /status tendermint endpoint and chain_id which is set to node_info.network from the same endpoint.

So now the metric looks like:

blazar_blocks_to_upgrade_height{chain_id="dimension_37-1",compose_file="...",hostname="...",upgrade_height="12038821",upgrade_name="test-metrics-labels-manas",upgrade_status="ACTIVE",upgrade_step="MONITORING",validator_address="CA7978B0C8D1968449053DA54166A8DA6A8DC67E",version="devel"} 1410

This metric along with the new labels will be useful in our case to suppress alerts when we know that an upgrade is under progress.

Test plan

We don't have any tests for metrics so I ran blazar on a dummy node and it seems to work fine. The sample metric above were fetched from that machine.