Add Vcpkg port version badge

[njakob]

I'm the author of vcpkg.link and I'm trying to improve the discoverability of Vcpkg ports. From my experience, such package managers have been helping developers to integrate libraries into their projects while keeping them up to date.

Therefore, this PR aims to add a shields.io badge that provides at a glance in the README which version of the library is available on Vcpkg.

Moreover, it provides a link to a page that contains extra details about the Vcpkg port of the library and how to use it.

---

Pull request checklist

Read the Contribution Guidelines for detailed information.

• [x] Changes are described in the pull request, or an existing issue is referenced.
• [x] The test suite compiles and runs without error.
• [x] Code coverage is 100%. Test cases can be added by editing the test suite.
• [x] The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header files single_include/nlohmann/json.hpp and single_include/nlohmann/json_fwd.hpp. The whole process is described here.

Please don't

• The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
• Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for this kind of bug). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
• Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
• Please do not open pull requests that address multiple issues.

[coveralls]

Coverage: 100.0%. Remained the same when pulling aad12e5f1098966667b9b6ae992c46148af74e8c on njakob:vcpkg-badge into 546370c9e778d99e7176641123e5cc1d0b62acab on nlohmann:develop.

[nlohmann]

Thanks!