refactor: fix analyzer code style warnings

[fischerscode]

New Pull Request Checklist

• I am not disclosing a vulnerability.
• I am creating this PR in reference to an issue.

Issue Description

This PR fixes the trivial, non breaking analyzer infos.

Related issue: #733

Approach

Mostly I just let the ide fix it.

TODOs before merging

- [ ] Make sure the change to _ParseLiveListElementWidgetState did not break anything.

[parse-github-assistant]

Thanks for opening this pull request!

• 🎉 We are excited about your hands-on contribution!

[fischerscode]

Each Prefer using lowerCamelCase for constant names. info, might require a breaking change.

[codecov]

Codecov Report

Merging #734 (aa7c8df) into master (a5224aa) will increase coverage by 6.93%.
The diff coverage is 11.68%.

@@            Coverage Diff             @@
##           master     #734      +/-   ##
==========================================
+ Coverage    3.34%   10.28%   +6.93%     
==========================================
  Files           4       48      +44     
  Lines         269     2810    +2541     
==========================================
+ Hits            9      289     +280     
- Misses        260     2521    +2261     

Impacted Files	Coverage Δ
packages/dart/lib/src/network/dio_adapter_io.dart	0.00% <ø> (ø)
packages/dart/lib/src/network/parse_client.dart	20.00% <0.00%> (ø)
...ackages/dart/lib/src/network/parse_dio_client.dart	0.00% <0.00%> (ø)
...ckages/dart/lib/src/network/parse_http_client.dart	5.12% <0.00%> (ø)
...ackages/dart/lib/src/network/parse_live_query.dart	0.91% <0.00%> (ø)
packages/dart/lib/src/objects/parse_base.dart	37.61% <0.00%> (ø)
packages/dart/lib/src/objects/parse_config.dart	0.00% <0.00%> (ø)
packages/dart/lib/src/objects/parse_error.dart	0.00% <ø> (ø)
packages/dart/lib/src/objects/parse_file.dart	0.00% <0.00%> (ø)
packages/dart/lib/src/objects/parse_file_web.dart	0.00% <0.00%> (ø)
... and 55 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a5224aa...aa7c8df. Read the comment docs.

[fischerscode]

Merging #734 (769e900) into master (1280ce3) will decrease coverage by 0.03%.

I think due to the introduction of defaultParseFileConstructor.

[mtrezza]

Kindly request a review when this is ready; not sure if you are currently waiting for review

[fischerscode]

I'll have to test, if this really does not break the animation.

Didn't test it yet. I'll request a review when I did.

[fischerscode]

Make sure the change to _ParseLiveListElementWidgetState did not break anything.

It works as expected, but I'll revert the change since it would be breaking. Older versions of Flutter (before v2.2.0-10.1.pre) require vsync

[fischerscode]

codecov should be fine. Might be due to more compact format or fewer imports.

[fischerscode]

Sorry @phillwiggins pressed the wrong button.

[mtrezza]

Could you please add the changelog entries to the corresponding packages? Entries should only go to the package in which the changes occur. We do separate releases and versioning now. See #668 (comment)

If this PR does not fix a bug, add a feature or improve performance, but is merely a refactor to get rid of recommended code style changes, then this would not lead to a changelog entry. The PR would simply be merged as something like refactor: fix analyzer code style warnings. I renamed the PR title; if that's incorrect, please rename accordingly.

[mtrezza]

Looks good! Let's try out this first dart - flutter combo release!

[mtrezza]

Oops, we forgot forgot to bump the package versions. I guess we can just wait for the next PR, probably #738, and do a release. Unless you feel like opening another PR just for the version bump.

[fischerscode]

Oops, we forgot forgot to bump the package versions.

Oops...

Unless you feel like opening another PR just for the version bump.

If you want, I can do it. It might be best to test it soon rather then later.

[mtrezza]

Sure, please go ahead

[fischerscode]

Sure, please go ahead

Link it to #733?