Fix build failure on Jetpack 4.6

[CoderHam]

Description:

Modify commit id of nlohmann/json to unblock jetpack 4.6 build for ORT 1.8.1

Motivation and Context

• Why is this change required? What problem does it solve?

I was attempting a build with a specific commit (d14b08d) off master that enables TRT 8 support in ORT 1.8.1. This specific compilation issue is seen on a Jetson Xavier

In file included from /triton/onnxruntime/onnxruntime/test/providers/kernel_def_hash_test.cc:65:0:
/triton/onnxruntime/cmake/external/json/single_include/nlohmann/json.hpp: In member function ‘void nlohmann::detail::serializer<BasicJsonType>::dump_escaped(const string_t&, bool) [with BasicJsonType = nlohmann::basic_json<>]’:
/triton/onnxruntime/cmake/external/json/single_include/nlohmann/json.hpp:15817:10: error: ‘%.2X’ directive output may be truncated writing between 2 and 8 bytes into a region of size 3 [-Werror=format-truncation=]
     void dump_escaped(const string_t& s, const bool ensure_ascii)
          ^~~~~~~~~~~~
/triton/onnxruntime/cmake/external/json/single_include/nlohmann/json.hpp:15817:10: note: directive argument in the range [0, 2147483647]
In file included from /usr/include/stdio.h:862:0

• Fixes compiler error: directive output may be truncated writing between 2 and 8 bytes nlohmann/json#2572

This is required by Triton Inference Server for supporting the Onnxruntime backend on Jetson.
cc @askhade

[jywu-msft]

this is just the manifest. but did you update the submodule itself?
i'm in the process of setting up a device with jetpack 4.6 to repro and validate.

[CoderHam]

Updated the submodule as well

[ghost]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

❌ CoderHam sign now
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[snnn]

Let's hold on this. The new one is not released yet. @faxu and @pranavsharma may have concerns.

[jywu-msft]

I made a PR for silencing the build warning, if we don't want to update the submodule to unreleased version.
#8701