Add MediaWiki authentication to node

[slifty]

This PR sets the stage for moving MediaWiki authentication logic out of shell and into the mw2pdf code base. Specifically, it introduces a new MediaWikiSession module which will allow us to separate the auth + rendering of a given page from the collation logic.

This also begins to refactor the code base a bit, moving us to node modules and starting to add some directory structure for code organization.

The new code is not integrated / run by a calling agent, but I confirmed it works by running the following in a sandbox.js file (node sandbox.js) against an instance of torque-devenv.

import { MediaWikiSession } from './classes/MediaWikiSession.js'

async function x() {
  const session = new MediaWikiSession()
  const apiUrl = 'http://127.0.0.1/LLIIA2020/api.php'
  await session.authenticate('admin', 'admin_password', apiUrl)
  await session.generatePdf('http://127.0.0.1/LLIIA2020/index.php')
}

x()

[slifty]

I decided not to add docblocks to individual methods since I believe they're somewhat auto-documented, but would be happy to add that in if desired.

[slifty]

An overall thought: some methods use "options" objects (e.g. `function doSomething({ firstParam, secondParam}) where others use traditional parameters. This is not inherently incorrect, but I want to do a pass to make sure there is a rhyme / reason to it.

This StackOverflow thread is a good resource when identifying rules of thumb

UPDATE: I decided to only use the options object in one method that had more than 4 parameters.

[slifty]

Little thing but lets remove this whitespace (we really need a linter soon!

[slifty]

Would be nice to write tests for all these utility methods, but we don't have tests set up yet. Once #20 is done lets come back and fix that deficit.

[slifty]

Gonna merge this in!