tidy: use modernize-use-raw-string-literal #25110

Refactor and turn on modernize-raw-string-literal. See https://clang.llvm.org/extra/clang-tidy/checks/modernize-raw-string-literal.html. This is a bit noisy, but I think ultimately worth it.

The motivation is to replace barely-(human)-parseable code like:

HelpExampleCli("logging", "\"[\\\"all\\\"]\" \"[\\\"http\\\"]\"")
+ HelpExampleRpc("logging", "[\"all\"], [\"libevent\"]")

with more-readable code like:

HelpExampleCli("logging", R"("[\"all\"]" "[\"http\"]")")
+ HelpExampleRpc("logging", R"(["all"], ["libevent"])")

while keeping the same output. i.e:

Examples:
Examples:
> bitcoin-cli logging "[\"all\"]" "[\"http\"]"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id": "curltest", "method": "logging", "params": [["all"], ["libevent"]]}' -H 'content-type: text/plain;' http://127.0.0.1:8332/

Note that we already sporadically use raw string literals in the code base.

Just my opinion, but using R"" for any cases where we'd otherwise have three backslashes in a row ("\\\"") makes sense, but where it's just escaping an individual backslash or quote, it doesn't seem that useful to me.

<!--e57a25ab6845829454e8d69fc972939a-->

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

<!--174a7506f384e20aa4161008e828411d-->

Conflicts

Reviewers, this pull request conflicts with the following ones:

• #25276 (doc: Fix typo in importdescriptors by KolbyML)
• #25218 (refactor: introduce generic 'Result' classes and connect them to CreateTransaction and GetNewDestination by furszy)
• #24162 (rpc: add require_checksum flag to deriveaddresses by kallewoof)
• #24161 (rpc/doc: describe using combo(privkey) to get checksum and then list … by kallewoof)
• #23319 (rpc: Return fee and prevout (utxos) to getrawtransaction by dougEfresh)
• #22838 (descriptors: Be able to specify change and receiving in a single descriptor string by achow101)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

<!--cf906140f33d8803c4a75a2196329ecb-->

🐙 This pull request conflicts with the target branch and needs rebase.

_{Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".}

Exlente