feat(grpc): adding is pruned and pruning height in blockchain info API

[kehiy]

Related issue

• Fixes Adding Prune information to BlockchainInfo API #1418

[kehiy]

@Ja7ad Hi, change requests fixed, please review.

[b00f]

To be compatible with Bitcoin RPC, let's add these information to the blockchain-info. Check here: https://developer.bitcoin.org/reference/rpc/getblockchaininfo.html

[kehiy]

@b00f Also, why we need to be compatible with Bitcoin RPC? We are not a fork or L2.

Also no bitcoin application uses Pactus. so whats the reason to be compatible?

[b00f]

I think pruning information fits better in BlockchainInfo rather than NodeInfo. Regarding Bitcoin compatibility, many developers are familiar with Bitcoin, so we should create something that looks familiar and is better organized.

[kehiy]

@b00f Blokchain info contains the chain info which is shared, node info contains the info about one node which is not shared between all nodes.

[kehiy]

Note: we decided that to move these info to blockchain info instead of node info since it will be mostly used there, using this info you can find you whether this node can provide info about old blocks or not. In this way caller can check this even if node info API is disabled.

Note2: we moved pruning height logic to store from state.