[clang-tools-extra] [clang-tidy] Add a fully custom message to `bugprone-unsafe-functions` (PR #162443)

[Donát Nagy via cfe-commits]

================
@@ -69,6 +69,11 @@ Potentially Breaking Changes
   - `CharTypdefsToIgnore` to `CharTypedefsToIgnore` in
     :doc:`bugprone-signed-char-misuse
     <clang-tidy/checks/bugprone/signed-char-misuse>`
+  
+- Modified the custom message format of :doc:`bugprone-unsafe-functions
+  <clang-tidy/checks/bugprone/unsafe-functions>` by hiding the default suffix
+  when the reason starts with the character `>` in the `CustomFunctions` option.
----------------
NagyDonat wrote:

Here and elsewhere ensure that code fragments are surrounded by _doubled_ backtick characters (two before the code fragment + two after it) because in RST single backticks creates links and you need doubled backticks to use monospace font.

Note that this differs from markdown (e.g. github comments) where monospace (code) text is marked by single backticks (while links use a completely different format: `[text](url)`).

https://github.com/llvm/llvm-project/pull/162443