Replace Paver quality and js_test commands

[salman2013]

Paver is deprecated, and we aim to fully remove it soon. You can find more details here:

Paver deprecation issue
Paver removal PR

A few Paver commands remain in the edx-platform, and to proceed with its removal, we've replaced the following Paver commands with equivalent Make commands:

1. Replaced paver run_pep8 with pycodestyle
2. Replaced paver run_eslint
3. Replaced paver run_stylelint
4. Replaced paver run_xsslint
5. Replaced paver run_pii_check
6. Replaced paver check_keywords
7. Replaced paver test_js* and paver diff_coverage

How to Test This PR:

In the edx-platform directory, you can use the following terminal commands to check for linting issues in Python and JavaScript files. Make sure your virtual environment is activated before running these commands.

make pycodestyle
make eslint
make stylelint
make xsslint
make pi_check
make check_keyword
make test-js
make test-coverage
make quality-test

For more details, please refer to the ticket: Replace paver quality and js_test commands

[salman2013]

@feanil @kdmccormick
Should we remove the paver tests as well like https://github.com/openedx/edx-platform/tree/master/pavelib/paver_tests?

[kdmccormick]

@salman2013 as you remove Paver commands, please remove the tests that correspond to those commands.

[kdmccormick]

Thanks for the PR @salman2013, but this only goes part of the way. The goal of #35159 is not only to get rid of the paver ... commands. The goal is get rid of all the Python code that runs our quality checks. In the end, we should be able to delete the whole pavelib directory.

Keep in mind that there are several things that pavelib code did that are now completely unnecessary, for example:

• junit.xml -- I don't know if we need to write this file any more. If nothing is obviously using it, it can be deleted.
• violation counts -- There was a time when all checks had "violation limits", so we would need to keep track of the violation count, and then fail only if the count exceeded the limit. For many checks, the violation limit is now zero. If the violation limit for a check is zero, then that check can be simplified, since any violation is enough to fail it.

I recommend starting with one simple check, such as pycodestyle, and see if you can get that running without any Python scripts involved.

[salman2013]

@kdmccormick This PR is ready for another pass. Please take a look thanks.

[kdmccormick]

Fantastic work so far. Really happy to see these running without Paver.

[salman2013]

@kdmccormick I believe this PR is ready for another pass. Please take a look thanks.

[kdmccormick]

Most of this feedback is straightforward, except the very last item regarding subprocess.run. I'm happy to go over that in our sync tomorrow morning if my comment isn't clear.

[salman2013]

@kdmccormick Thanks for reviewing the PR, I have fixed all your comments, and the PR is ready for another pass.