Yda 6068 add csv output to troubleshoot tool

[FuHsinyu]

1. Run in human readable output (by default):
   python3 troubleshoot-published-data.py -m human or python3 troubleshoot-published-data.py
2. Run in CSV output:
   python3 troubleshoot-published-data.py -m csv

Documentation update: UtrechtUniversity/yoda#551

[FuHsinyu]

Currently, there is an error when you run the troubleshooting tool with python3, because we upgraded python2 to python 3. See the code local_data_uni = local_data.decode("utf-8"). A workaround is to use local_data_uni = local_data#.decode("utf-8") in publication-troubleshoot.py

[FuHsinyu]

Currently, a potential improvement is that: when outputting a failed package with a failed reason (e.g, missing AVUs), in human mode, the reason will be displayed at the top of the output. Rather, I wonder if it be nice to have the reason combined with the package output. Let me know what you think.
e.g,
Troubleshooting package No.1:
Missing AVU found...
Troubleshooting package No.2:
MIssing landing page.

Results for: NO.1
Package FAILED one or more tests:
Schema Check: Pass
Missing AVUs Check: Fail
Unexpected AVUs Check: Pass
Version DOI Check: Fail
Landing Page Check: Pass
Combi JSON Check: Pass

Results for: NO.2
Package FAILED one or more tests:
Schema Check: Pass
Missing AVUs Check: Pass
Unexpected AVUs Check: Pass
Version DOI Check: Fail
Landing Page Check: Fail
Combi JSON Check: Pass

[stsnel]

This looks good in general 👍! Can you remove trailing whitespace in troubleshoot_data.r and have a look at the comment above?