feat: add --fix option

Signed-off-by: ktro2828 <kotaro.uetake@tier4.jp>

Author: ktro2828

docs/cli/t4sanity.md

@@ -14,6 +14,7 @@ $ t4sanity -h
 │ --revision            -rv      TEXT  Specify if you want to check the specific version. [default: None]               │
 │ --exclude             -e       TEXT  Exclude specific rules or rule groups. [default: None]                           │
 │ --strict              -s             Indicates whether warnings are treated as failures.                              │
+│ --fix                                Attempt to fix the issues reported by the sanity check.                          │
 │ --install-completion                 Install completion for the current shell.                                        │
 │ --show-completion                    Show completion for the current shell, to copy it or customize the installation. │
 │ --help                -h             Show this message and exit.                                                      │
@@ -65,6 +66,15 @@ $ t4sanity <DATA_ROOT>
 +-----------+---------+--------+--------+---------+----------+
 ```
 
+### Exclude Checks
+
+With `-e; --exclude` option enables us to exclude specific checks by specifying the **rule IDs or groups**:
+
+```shell
+# Exclude STR001 and all FMT-relevant rules
+t4sanity <DATA_ROOT> -e STR001 -e FMT
+```
+
 ### Strict Mode
 
 Basically, rules whose **severity is WARNING** will be treated as success.
@@ -76,25 +86,27 @@ With `-s; --strict` option enables us to treat warnings as failures:
 t4sanity <DATA_ROOT> -s
 ```
 
-### Exclude Checks
+### Fix Issues
 
-With `-e; --excludes` option enables us to exclude specific checks by specifying the **rule IDs or groups**:
+With `--fix` option enables to fix issues automatically:
 
 ```shell
-# Exclude STR001 and all FMT-relevant rules
-t4sanity <DATA_ROOT> -e STR001 -e FMT
+# Fix issues automatically
+t4sanity <DATA_ROOT> --fix
 ```
 
 ### Exit Status Logic
 
 `t4sanity` CLI returns the exit code based on the following conditions:
 
-| Condition                                                               | `--strict`        | Exit Code | Notes                                               |
-| ----------------------------------------------------------------------- | ----------------- | --------- | --------------------------------------------------- |
-| At least one `Severity.ERROR` rule failed                               | N/A               | 1         | Always fails the run                                |
-| At least one `Severity.WARNING` rule failed, no `Severity.ERROR` failed | `False` (default) | 0         | Run is considered successful, warnings are reported |
-| At least one `Severity.WARNING` rule failed, no `Severity.ERROR` failed | `True`            | 1         | Treat warnings as failures; exit with failure       |
-| All rules passed or skipped                                             | N/A               | 0         | Run is considered successful                        |
+| Condition                                                                          | `--strict`        | `--fix` | Exit Code | Notes                                                                     |
+| ---------------------------------------------------------------------------------- | ----------------- | ------- | --------- | ------------------------------------------------------------------------- |
+| At least one `Severity.ERROR` rule failed                                          | N/A               | `False` | 1         | Always fails the run                                                      |
+| At least one `Severity.ERROR` rule failed, but fixed                               | N/A               | `True`  | 0         | Run is considered successful, error reasons are reported and `Fixed=true` |
+| At least one `Severity.WARNING` rule failed, no `Severity.ERROR` failed            | `False` (default) | N/A     | 0         | Run is considered successful, warnings are reported                       |
+| At least one `Severity.WARNING` rule failed, no `Severity.ERROR` failed            | `True`            | `False` | 1         | Treat warnings as failures; exit with failure                             |
+| At least one `Severity.WARNING` rule failed, no `Severity.ERROR` failed, but fixed | `True`            | `True`  | 0         | Run is considered successful, warnings are reported and `Fixed=true`      |
+| All rules passed or skipped                                                        | N/A               | N/A     | 0         | Run is considered successful                                              |
 
 ### Dump Results as JSON