pb: Config service added: minimum selection version for upload added.

[Qweder93]

Change-Id: I2fdf1b1a5555e102c8f9a53af0d18b54786d23e7

What: added minimum selection version to nodestats

Why: all minimum selection versions from trusted satellites will be compared and newest version will be shown
as version on which node still won't be disqualified, but would not receive new data, just storing.

Please describe the tests:

• Test 1:
• Test 2:

Please describe the performance impact:

Code Review Checklist (to be filled out by reviewer)

• NEW: Are there any Satellite database migrations? Are they forwards and backwards compatible?
• Does the PR describe what changes are being made?
• Does the PR describe why the changes are being made?
• Does the code follow our style guide?
• Does the code follow our testing guide?
• Is the PR appropriately sized? (If it could be broken into smaller PRs it should be)
• Does the new code have enough tests? (every PR should have tests or justification otherwise. Bug-fix PRs especially)
• Does the new code have enough documentation that answers "how do I use it?" and "what does it do?"? (both source documentation and higher level, diagrams?)
• Does any documentation need updating?
• Do the database access patterns make sense?

[egonelbre]

There's no description on why and how this will be used.

Similarly this would fragment where minimum version is defined. The satellite does not know this information.

[egonelbre]

@Qweder93 I adjusted the naming a bit.

was involved in design

[Erikvv]

Is this still relevant?

[Erikvv]

Per the PR description

all minimum selection versions from trusted satellites will be compared and newest version will be shown
as version on which node still won't be disqualified, but would not receive new data, just storing."

The name "upload" seems the opposite of this, we usually call this download. To avoid this ambiguity maybe call it "storeNewPieces"?