Typed configuration

[nulls]

          Good by for now, anyway need to go step-by-step here. I think we will need a fixed schema with keys that would be rule names, for example:

[LONG_LINE]
    enabled=true

or

"LONG_LINE": {
     "enabled": "true"
}

Originally posted by @akuleshov7 in #1686 (comment)

---

• Analyze using EditorConfig as a source for diktat-analysis.yml #1829
• [request] Add capability to configure in-code instead of YAML #1041
• Support hierarchy in configurations
• Warn messages should be configurable (substitution)

[nulls]

We have two two plugins and one external spotless where we can configure rules.
We can use code-generation: we specify configuration in a single place and it generates configuration for gradle and maven plugins + classes for rules in diktat-rules.
Such approach also will allow to support different sources: old yml, editorconfig and in-code settings.