deps: update inspector_protocol to c149e90e9ff5bf7

[aduh95]

Hopefully this should fix the linux-coverage GitHub Action.

To update it, I used the following commands:

rm -r tools/inspector_protocol
cp -r deps/v8/third_party/inspector_protocol tools/inspector_protocol
git add tools/inspector_protocol
git checkout -- tools/inspector_protocol/jinja2
git checkout -- tools/inspector_protocol/markupsafe
git commit
git cherry-pick 4662f67e3849d1e3d5127cc5ebc469d1febca57f

Then I had to update src/inspector/node_inspector.gypi to reflect the changes in tools/inspector_protocol/inspector_protocol.gni.

[targos]

See #27770

Last time I updated inspector_protocol, it was by copying the files that V8 keeps in https://github.com/nodejs/node/tree/master/deps/v8/third_party/inspector_protocol

[targos]

Also see https://github.com/nodejs/node/commits/master/tools/inspector_protocol for the fixes that we float on top of it.

[benjamingr]

Rubber stamp LGTM (and assuming Jinga 2 is now a dependency)

[targos]

In the current code on master, jinja2 is included with inspector_protocol. that's why we don't need to install it externally

[aduh95]

It seems there are a lot of breaking changes in the update, I'm starting to wonder if I haven't pick a challenge too big for my skills. inspector_protocol is now using the Chrome DevTools Protocol Library which is a quite different implementation, and it would require a lot of refactoring work.
@targos wdyt? do you think it's worth keeping up with the upstream version?

[github-actions]

This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open.