Use lintrunner

[justinchuby]

Adopt lintrunner for running all linters locally and in CI. https://github.com/suo/lintrunner

• Remove all formatting scripts in favor of lintrunner
• Updated readme with new instructions
• Run lintrunner -a to fix all lint errors
• Support SARIF results in Github

Nice SARIF error messages:

e.g. https://github.com/microsoft/onnx-script/security/code-scanning/335

[codecov]

Codecov Report

Merging #168 (d0ba635) into main (0b64a9e) will not change coverage.
The diff coverage is 90.00%.

@@           Coverage Diff           @@
##             main     #168   +/-   ##
=======================================
  Coverage   81.04%   81.04%           
=======================================
  Files          66       66           
  Lines        5133     5133           
=======================================
  Hits         4160     4160           
  Misses        973      973           

Impacted Files	Coverage Δ
onnxscript/backend/onnx_backend.py	78.39% <0.00%> (ø)
onnxscript/test/models/graph_attr.py	65.11% <100.00%> (ø)
onnxscript/test/onnx_backend_test.py	74.17% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[justinchuby]

@abock @gramalingam please take a look, thanks! I would like to make sure licensing and attribution is good for files under .lintrunner/

[titaiwangms]

What does new friends: newlines/grep do?

[gramalingam]

I would like to make sure licensing and attribution is good for files under .lintrunner/

Do you mean from a legal perspective? Let me defer that to Aaron. I guess it should not be a problem.

[github-advanced-security]

lintrunner found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.

[abock]

I would like to make sure licensing and attribution is good for files under .lintrunner/

Do you mean from a legal perspective? Let me defer that to Aaron. I guess it should not be a problem.

It's MIT licensed, so no issues here as long as the original license files, annotations, and copyrights are preserved.

However, is there a reason for including all the code in the repo? Can this be installed as a build dependency or should we submodule it?

I will do a deeper review tomorrow.

[justinchuby]

The original adapters are part of the pytorch repo. I guess we can create a package for these adapters? For now they live in https://github.com/justinchuby/lintrunner-adapters

[justinchuby]

Alternatively we can create a new repo in the ms org and share it as a submodule across the various onnx projects

[titaiwangms]

Alternatively we can create a new repo in the ms org and share it as a submodule across the various onnx projects

Feel like it makes more sense that each repo has its own adapters though. Or it could affect multiple repos, if one of the repo wanted a new formatting.

[justinchuby]

I agree. I feel we can allow max control by having the adapters local to each repo. If we see a more reusable pattern we can then move them to the same place.

I thought about it again and realized things are much easier and cleaner with a package. I created https://pypi.org/project/lintrunner-adapters/.

[justinchuby]

Normalized line endings to POSIX

[justinchuby]

@gramalingam PTAL. I think this PR is now purely formatting. Should be straight forward (hopefully)