src: apply clang-tidy rule modernize-make-unique

[gengjiawen]

Apply clang-tidy rule https://clang.llvm.org/extra/clang-tidy/checks/modernize-make-unique.html

And also in Item 21: Prefer std::make_unique and std::make_shared to direct use of new.

• Compared to direct use of new, make functions eliminate source code duplication, improve exception safety, and, for std::make_shared and std::allocate_shared, generate code that’s smaller and faster.
• Situations where use of make functions is inappropriate include the need to specify custom deleters and a desire to pass braced initializers.

cc @addaleax @refack @bnoordhuis

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

[refack]

RSLGTM % two nits

[danbev]

CI: https://ci.nodejs.org/job/node-test-pull-request/21318/

[danbev]

@gengjiawen Would you be able to rebase this and fix the conflict reported? Thanks

[gengjiawen]

@danbev I can fix this evening :)

[gengjiawen]

@danbev done. Can you also help to re-trigger #26496 Jenkins CI ? Thanks.

[danbev]

Re-based CI: https://ci.nodejs.org/job/node-test-pull-request/21461/

[gengjiawen]

@danbev I forced push because travis-ci found a lint issue ? Do you need to re-trigger this again ? Sorry for this inconvenience.

[BridgeAR]

Landed in 575e086 🎉

[BridgeAR]

This does not land cleanly on v11. It seems to rely on other commits (e.g. #26306) that should be backported first. Please open a manual backport for it or change the labels accordingly.

[gengjiawen]

I am not familiar with backport process, how should I do it ?

[BridgeAR]

If a PR requires manual backports, we should first identify what code it relies upon. There are other PRs that should be backported first as the one that I pointed out. Otherwise there are more conflicts and they become worse over time.

So this one should likely not be the first to be backported. @joyeecheung recently added a tool to node-core-utils that is able to identify them (see https://asciinema.org/a/221244).

A backport itself is just a PR which targets the staging branches of the release line. In this case v11.x-staging instead of master.

[refack]

I opened a backport PR for this: #26651