fix(cloud_firestore_odm): Update ignored lints in generated files

[Rexios80]

Description

Changes:

• Adds some missing lint rules to the ignore_for_file list: require_trailing_commas, prefer_single_quotes, prefer_double_quotes, use_super_parameters
• Converts all double quotes in generated files to single quotes for consistency

Notes:

• I would like to not exclude generated files from analysis, but this project's enforcement of implicit-dynamic seems to make that impossible without more changes that are outside the scope of this PR
  • Especially with this package, it's really easy to generate code with errors, and excluding generated files from analysis hides those. For example, freezed.g.dart was missing the import for package:cloud_firestore/cloud_firestore.dart, but the analyzer didn't make that obvious since the file was excluded from analysis.
  • Excluding generated files from analysis makes it impossible to enforce consistent style such as single vs double quotes. This doesn't matter for projects that use the generator, but since this is the generator it would be nice to enforce it.
  • Pana (the package analyzer) doesn't respect analysis exclusions, so you run the risk of having code pass analysis locally, but losing points on pub.dev
• I have a tool that needs to know if a project requires flutter based on the pubspec, so I added it to the dependencies for cloud_firestore_odm_generator. If you would like me to remove it just let me know.

Related Issues

N/A

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[rrousselGit]

You should be able to do this without modifying the ODM by configuring your build.yaml
The build.yaml allows adding custom lines of code at the top of the generated .g.dart files.

But these changes are reasonable, so I'll accept them.

[rrousselGit]

LGTM