Update pvesh module_util to reflect upstream changes

[SniperCZE]

There was a little change in output of pvesh in august (no 200 status line in result when OK + default json export changed to pretty tables) which needs to be reflected in pvesh ansible module.

[HenrikWMG]

Just wanna say, that i applied that Pull Request on my setup. it solved my Issues. Ty

[lae]

Some tests are failing for PVE 4.x it looks like, but I have #33 open with regards to that.

PVE 5.x tests still seem to be failing here however: https://travis-ci.org/lae/ansible-role-proxmox/jobs/424784386#L1594

If you can take a look at that and fix that, I'll merge this - otherwise it might still be a bit before I can take a closer look at what might be causing that failure.

[lae]

notes

root@proxmox-test:~# /usr/bin/pvesh get access/users/root@pam --output=json
Use of uninitialized value in string eq at /usr/share/perl5/PVE/CLIFormatter.pm line 390.
{"enable":1,"groups":[]}
root@proxmox-test:~# /usr/bin/pvesh get access/users/root@pam --output=json 2>/dev/null
{"enable":1,"groups":[]}

[lae]

someone filed a bug upstream that's most likely related (same error, same line) https://bugzilla.proxmox.com/show_bug.cgi?id=1914

return if $result_schema->{type} eq 'null'; from /usr/share/perl5/PVE/CLIFormatter.pm

[lae]

Added comment to the bug and the small hotfix https://bugzilla.proxmox.com/show_bug.cgi?id=1914#c1

Patch seems to have worked, it looks like I needed to update the tests to get JSON output from pvesh as well so I'm waiting for that build to finish before merging.