move analysis_options.yaml into packages

[devoncarew]

• move analysis_options.yaml into packages
• regenerate mono_repo files

This catches a number of diagnostics in the shelf packages (mostly instances of comment_references diagnostics).

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[kevmoo]

But don't we like having fewer analysis_options files? Is this to work-around an analyzer bug?

[devoncarew]

But don't we like having fewer analysis_options files?

Well, fewer analysis configurations for sure. Most of these are just include: package:dart_flutter_team_lints/analysis_options.yaml, which isn't really a maintenance issue.

Is this to work-around an analyzer bug?

I think there is a bug here, because I see different analysis results w/ one top level analysis file vs. the same configs, one in each package.

But I like having the packages be self-contained - not depend on files above them in the repo. And this also removes the persistent analysis diagnostic you see if you open the whole repo; the top-level analysis options file can't resolve its reference to package:dart_flutter_team_lints.