add a top level pubspec to silence the analysis_options.yaml diagnostic

[jakemac53]

Up for discussion, it isn't super ideal but I don't know of a simpler/better option. Getting quite tired of having the persistent diagnostic that package:lints can't be resolved.

One alternative is creating a whole subdirectory instead and moving the file there, but then it wouldn't apply automatically to all packages, we would have to manually add an analysis_options.yaml to each and import that one, and may forget to do so when adding new packages.

One advantage of the alternative approach though would be that we would get a warning if forgetting to include package:lints from any given package (they do each have to add it or else the import doesn't resolve correctly).

[natebosch]

We could also consider putting a copy of the file in each package directory with some automation to ensure it's kept in sync, perhaps with mono repo? cc @kevmoo

Or does it work to put symlinks in each package directory?

I'd be fine with this approach too - I don't have strong opinions about what the top level directory of the repo looks like.

[jakemac53]

For now I think this is the simplest option