Providing other analysis_options.yaml to dart analyze

[EvgheniiBeriozchin]

I am exploring writing a linting package with a more complex rule application logic. Specifically, I'd need to run a stricter analysis of the dart code without actually applying these rules to the project (for ex. not displaying them in VSCode).

I was thinking whether you could add the option to choose the specification yaml in dart analyze similarly to how we can choose which file to analyze. I'd imagine this option would override the existing analysis_options.yaml and all its "children".

Thanks.