Updated known-good tests and npm audit fixes

[lhstrh]

No description provided.

[lhstrh]

Looks like there is an issue with the test that checks whether we correctly handle outdated versions of the pylint dependency. Not sure what's the problem though -- it could be an issue of the CI environment being configured differently. Maybe @petervdonovan has an idea?

[edwardalee]

These changes look good to me, but there are still test failures.

[edwardalee]

Do we really need the test-dependencies-outdated test? It seems to be trying to download a very old version of pylint. The name of this test suggests the test itself is outdated.

[lhstrh]

The test addresses the scenario where the user has an outdated version of pylint installed. This is a different situation compared to the one where the user doesn't have it installed at all. Hence the separate test. The test itself is not outdated.

[petervdonovan]

I agree with Marten's explanation. The only thing I have to add is that according to the test framework, the expected update or install function is not being called in response to pylint being out of date.

This can happen if the CI environment has changed in such a way that pylint is not being brought out of date successfully by the "downgrade dependencies" step. For example, this could be because Ubuntu no longer allows managing global (outside a virtual environment) dependencies using pip.

Unfortunately I am not currently available to look into this in more detail.

[edwardalee]

Any suggestion for fixing it? Otherwise, I'm inclined to delete the test.