[BUG] npx behavior in CI environments

Problem

This isn't really a bug, but raising it to discuss the potential impact of changes to `npx` in CI environments. Current Behavior: [code block] `npx -y mocha` works to get the automatic install behaviour, but that would require users to update their CI scripts. Also, `npx -y mocha` errors in npm@6 with: [code block] I think that would complicate the logic required in CI scripts when running across multiple Node.js/npm versions. _Just using Mocha as an example. In Node.js, we use npx in our GH Actions configuration, which I suspect would be broken when GH Actions updates to use a version of Node.js containing npm@7._ Expected Behavior: - Unsure, but curious if there could be a workaround that removes the need for users to edit their scripts. Steps To Reproduce: - `npx <module>` in a CI enironment. Environment: - All CI environments /cc @MylesBorins @richardlau