feat: Updates for release 0.2.0

[mpkander]

Tap on "Preview" ⤴

And choose one of the templates:

• Bugfix PR
• New feature PR
• Documentation update PR

[dzmitry-struk-surf]

LGTM

[plastb1r]

@mpkander Can we add a couple more exceptions?
Propose this list:

prefer-widget-private-members: false
Many of flutter widgets themselves use public fields and methods that can be used elsewhere to read configuration, retrieving them by context. I agree that, like any public entity, their use should be limited, but they should not be banned.

prefer-correct-error-name: false
There is another lint that advises prescribing the type of what we are trying to intercept. For example, "on Exception". And therefore, it seems redundant to prescribe the name of the variable.

avoid-empty-setstate: false
There is a practice of using setState when it is called empty at the end of the callback, when manipulations to change the state have already been performed in front of it, to decrease nesting of setState.

no-empty-block: false
Sometimes its more convenient to pass an empty callback for not making a field nullable.

Also, we can expand prefer-correct-identifier-length exceptions with 'n', 'e', 'x', 'y', 'z' for indexing, exceptions and pixels/planes working, respectively