Moving Pylint guidelines checker from sdk-for-python to here

[scbedd]

@tjprescott just FYI

Can you please try using the external package (instead of the inserted into path as seen in rcfile usage?)

• There are a couple test failures that are outstanding that I need to address (they are pointed at non-existent guidelines pages now due to rework of azure-sdk github.io page)
• I also need to rename from pylint_custom_plugin to pylint_guidelines_checker.

[tjprescott]

Adding @l0lawrence as reviewer since she's working on pylint plugin stuff as well.

[tjprescott]

Also I think @l0lawrence already had a PR that fixed the broken links.

[check-enforcer-staging]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).