Clarify LFS size build info means capacity

[mk-pmb]

• This PR is for the dev branch rather than for master.
• This PR is compliant with the other contributing guidelines as well (if not, please describe why).
• I have thoroughly tested my contribution.
• The code changes are reflected in the documentation at docs/*.

Trivial clarification that the LFS build info means its capacity. For a while I was unsure about it because mine shows zero, so I was wondering if it might mean the amount used, or the start position.

[HHHartmann]

The branch also has to be based on dev. Maybe you can rebase it.

[mk-pmb]

Base branch should be fixed now. At first I had assumed the checkbox was about the Git tree, not the Github UI.

[marcelstoer]

I had assumed the checkbox was about the Git tree, not the Github UI.

They go hand-in-hand.

[HHHartmann]

This seems to be ok unless someone is parsing the output. In that case it would break that parser.

[TerryE]

I missed this one sorry. I've was just merging these changes and in doing do reviewed this node.c code. @HHHartmann there are weaknesses in this approach of mining data from the make to generate runtime configuration data:

1. This is denormalising information that is available elsewhere, for example you can enumerate the tables in ROM to list all included modules and other file and node API calls which give the correct runtime configuration values.
2. The answers returned can be just wrong. For example the LFS region size is based on the value in the Partition Table which can be different to the build default as this can be changed by editing the Partition Table after imaging or by the node.setpartitiontable() API call.