Remove mason-js dependency

Nobody has claimed this yet.

The `mason-js` dependency is unmaintained and frozen, but still currently used inside of `vtshaver`. It has been unmaintained since 2018. For a while it seemed like `mason-js` would again see maintenance (enough that security issues related to out-of-date binaries and `mason-js` JS dependencies could be mitigated). But, in effect, `mason-js` not been maintained since 2018 and therefore I think it is critical to [acknowledge this](https://github.com/mapbox/mason-js/commit/8159e7685c50b140c37cb905f158d6795d663ffd) and take action downstream (here).

So, my recommendation is to remove the dependence on `mason-js` in `vtshaver`.

To do this would involve:

- Removing `mason-js` from the `package.json`
- Removing the `mason-versions.ini`
- Implementing an alternative method for fetching up to date and reliable versions of dependencies that are currently being installed by `mason-js`

Start by reading package.json and mason-versions.ini, then inspect how mason-js is used inside vtshaver. Identify every dependency currently installed through mason-js and determine a reliable replacement before removing the dependency and versions file. Done means vtshaver obtains those dependencies without mason-js and remains functional.

Written by the indexing model from the issue text.