clang-tidy doc: add a note for every checker with an autofix

[sylvestre.ledru]

Summary

Currently, when looking at a checker documentation, we have to go back
to the whole list or look at the sources to figure out if an autofix
is available or not.

Feel free to propose a better wording

Here is the ugly way I used:
LIST=$(grep Yes list.rst|awk '{print $1}'|cut -d\` -f2)
or f in $LIST; do cat /tmp/a.txt >> $f.rst; done

with /tmp/a.txt containing the text

[Eugene.Zelenko]

It'll be reasonable to use two spaces indent. At least this is what mostly used for code blocks. Options are exceptions, but will be good idea to reformat them eventually.

[sylvestre.ledru]

2 spaces instead of 4

[alexfh]

clang-tools-extra/docs/clang-tidy/checks/abseil-duration-conversion-cast.rst

29–35 ↗

(On Diff #256943)

A few problems with this approach:

1. Some checkers' docs already have more specific wording about the fix. Adding a generic phase doesn't make the documentation look neat.
2. The "callable with --fix" part isn't relevant to all clang-tidy frontends. Even for the CLI a reference to the documentation would be more helpful than a mention of this command-line option (there are other relevant options and ways to apply a fix - --fix-errors, -export-fixes + the clang-apply-fixes tool, etc.).

My proposal is to add a mandatory Automatic fixes or Suggested fixes section to all checker documentation files, require the authors to describe the nature of the fix more thoroughly, and use consistent wording when there is no fix. E.g.

Automatic Fixes
^^^^^^^^^^^^^

The check doesn't provide an automatic fix.

or

Automatic Fixes
^^^^^^^^^^^^^

The check provides suggested fixes. See the documentation above for the details.

or

Automatic Fixes
^^^^^^^^^^^^^

The check provides suggested fixes in the following cases:
1.
2.
3.

WDYT?

[sylvestre.ledru]

Makes sense.
I will give it a try :)
thanks

[sylvestre.ledru]

Doing it by hand. @alexfh please let me know if you would be ok with it
(I will do it by hand)

[sylvestre.ledru]

@alexfh ping

[sylvestre.ledru]

@alexfh ping

[sylvestre.ledru]

has been reverted

clang-tools-extra/docs/clang-tidy/checks/misc-unused-parameters.rst

 
 .. option:: StrictMode
 
    When zero (default value), the check will ignore trivially unused parameters,
    i.e. when the corresponding function has an empty body (and in case of
    constructors - no constructor initializers). When the function body is empty,
    an unused parameter is unlikely to be unnoticed by a human reader, and
    there's basically no place for a bug to hide.
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.

clang-tools-extra/docs/clang-tidy/checks/modernize-avoid-bind.rst

.. code-block:: c++
   int foo() {
     std::function<int(int,int)> ignore_args = [](auto&&...) { return add(2, 2); }
     return ignore_args(3, 3);
   }
 
 which is correct.
   
 This check requires using C++14 or higher to run.
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.

clang-tools-extra/docs/clang-tidy/checks/modernize-deprecated-ios-base-aliases.rst

 Deprecated member type               Replacement
 ===================================  ===========================
 ``std::ios_base::io_state``          ``std::ios_base::iostate``
 ``std::ios_base::open_mode``         ``std::ios_base::openmode``
 ``std::ios_base::seek_dir``          ``std::ios_base::seekdir``
 ``std::ios_base::streamoff``          
 ``std::ios_base::streampos``         
 ===================================  ===========================
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.

clang-tools-extra/docs/clang-tidy/checks/modernize-loop-convert.rst

 As range-based for loops are only available since OpenMP 5, this check should
 not been used on code with a compatibility requirements of OpenMP prior to
 version 5. It is **intentional** that this check does not make any attempts to
 exclude incorrect diagnostics on OpenMP for loops prior to OpenMP 5.
 
 To prevent this check to be applied (and to break) OpenMP for loops but still be
 applied to non-OpenMP for loops the usage of ``NOLINT`` (see
 :ref:`clang-tidy-nolint`) on the specific for loops is recommended.
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.

clang-tools-extra/docs/clang-tidy/checks/modernize-make-shared.rst

.. option:: IncludeStyle
 
    A string specifying which include-style is used, `llvm` or `google`. Default
    is `llvm`.
 
 .. option:: IgnoreMacros
 
    If set to non-zero, the check will not give warnings inside macros. Default
    is `1`.
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.

clang-tools-extra/docs/clang-tidy/checks/modernize-use-bool-literals.rst

 
 Options
 -------
 
 .. option:: IgnoreMacros
 
    If set to non-zero, the check will not give warnings inside macros. Default
    is `1`.
+
+Automatic Fixes
+^^^^^^^^^^^^^^^
+
+The check provides suggested fixes. See the documentation above for the details.