Smart storage values based on assumed chain and chainstate values

[jarolrod]

When a prune target is set, that limits how much storage is taken up by blocks. But there is still other data such as the chainstate. This moves us away from wrongly conveying that the prune target is how much data will be taken up, and instead conveys how much data will be taken up considering the prune target, assumed blockchain size, and assumed chainstate size. The assumed sizes are updated every release cycle.

Changes:

• Storage Location

  • The text that shows what the minimum amount of space needed is now displays assumed chainstate size + 1GB instead of just 1GB

• Storage Options

  • The default prune button is now 2GB + assumed chainstate size instead of just the prune target of 2GB
  • Store all data button is now the assumed blockchain size + assumed chainstate size instead of a hardcoded 550GB
  • Custom Prune button is now the prune target + assumed chainstate size instead of just the prune target set in detailed settings

• Storage Settings

  • The text of the Setting which is used to set a custom prune target is changed from "Storage limit (GB)" to "Block Storage limit (GB)" to convey this controls block storage specifically. The Custom prune button that then appears on the storage options page shows this prune target + assumed chainstate size

Master

Storage Location	Storage	Storage Settings	Custom Prune

PR

Storage Location	Storage	Storage Settings	Custom Prune

[jarolrod]

Updated from b1c639b to 5ead189, Compare

• Changes: rebased over main

[jarolrod]

cc @johnny9 @hebasto

[johnny9]

ACK 5ead189