Problem: The GUI interprets and displays the assumed chain sizes as decimal GB, but the first-run disk-space check converts the blockchain estimate as GiB. For pruned nodes, the warning also displays the full-chain estimate even though the check uses the lower of the prune target and that estimate. The release process likewise tells maintainers to measure both assumed sizes in GiB.
Fix: Add overflow-checked _MB and _GB byte-unit literals, use them for the GUI's existing decimal byte conversions and the assumed blockchain size, round the estimate used by the check up to GB for display, and document both assumed sizes in GB.
This PR revives the stale #29678.