Add ability to change rule configuration via comments

[AliSoftware]

Today we can disable and enable rules on the fly using comments like // swiftlint:enable rule_identifier.

It would be quite useful to also be able to change some rules' parameters via comments as well, especially to locally extend some limits without entirely disable that rule.

For example, one might have configured the file_length rule in its .swiftlint.yml to trigger a warning after 400 lines. But then for a specific file which happens to be like 480 lines, they want to allow going a little over the limit for that specific case.
They could // swiftlint:disable file_length but doing that means that if in the future the file grows to 1000 lines, it won't warn anymore.
It would be way better to be able to set a new limit of 500 for this file instead of disabling the rule.

---

We could imagine multiple syntaxes for that comment, like:

// swiftlint:param rule_identifier value
// swiftlint:rule_identifier value

But some rules might be able to configure more than just the warning/error level, so maybe we should come up with a more explicit syntax, like:

// swiftlint:rule_identifier warning:value error:value2
// swiftlint:trailing_whitespace ignores_empty_lines:true

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. Please comment to prevent this issue from being closed. Thank you for your contributions!

[ondrej-hanslik-csob-cz]

I don't think this is wise.
First of all, any coding guidelines should be equally valid for all files. If the warning limit is 400 lines, then 480 lines is wrong and should be fixed. That's why the warning should stay there. Increasing the limit is an easy solution but it is also a wrong solution. If you do such things, you can just disable the rule altogether.

If there actually are different group of files that need specific rules, then I would recommend separate swiftlint configurations for each group of files.