Refactor amalgamation workflow to avoid dangerous use of pull_request_target

[joycebrum]

Closes #3945

I've followed the approach recommended by Github Security Lab - Preventing pwn requests. This way the pull_request workflow won't have any write privilege that could be exploit.

I have tested the new workflow to add the comment in case of failure in the amalgamation workflow here https://github.com/joycebrum/json/pull/3, and it worked fine.

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 9380ab096ed8a9161749bc5b277bc8b9e92953ae on joycebrum:develop into b504dca35a6aac16c4596441a78024737bcc95c0 on nlohmann:develop.

[nlohmann]

Thanks a lot! I will merge once the CI runs through.