satellite/repair: improve logging

[littleskunk]

What: Improve the logging around failed repair.

satellite/0      12fbck97kq 01:36:35.511 | ERROR	repairer	repairer/repairer.go:95	repair worker failed:	{"Segment": "ZDY0Zjg1MDEtMjJkMC00YjI0LWI1YjItNmIyYzllZGIxOTRhL2wvcmVsZWFzZS1hbHBoYTE3LwI2ebiX+gjbGB9ZJFHU5/T0tgfN5zH9/f4B1GBDk9j9Vg==", "error": "repairer error: repairing injured segment: repairer error: couldn't download enough pieces, number of successful downloaded pieces (1) is less than required number (4)"

Why: At the moment the satellite prints out the encrypted path. It is hard to grep a logfile for the encrypted path. My hope is that with the new logging will allow us to grep, sort and count the binary value instead of the encrypted path. There is still one line that prints out the encrypted path so that we still have it if we need it.

Please describe the tests:

• Test 1:
• Test 2:

Please describe the performance impact:

Code Review Checklist (to be filled out by reviewer)

• 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?

[jtolio]

same comment as #3285

[stefanbenten]

At least with comparison to #3285 i would prefer to have a more straight logging in terms when to log the path. Sometimes its logged in front, sometimes at the end.

[stefanbenten]

To get it into the release, lets merge it as is and make a follow up PR @littleskunk