This PR is built off of dev/3.0.3 and requires that to be merged in first

This PR includes a many fixes and patches for various things:

• Fixes MWDK should warn users about invalid qset properties on creator save #120 - Qsets are now 'standardized' the same way that Materia Docker would standardize them. Much of the code for this standardization is heavily based off Materia Docker's code, so the behavior should be identical. Fields that are outside of what is expected in certain places (like 'options' within a question object, the issue I had) are now stripped and reported about in the console.
• Fixes Add preflight checks to help new widget authors #43 - This builds off a lot of previous work to create preflight checks that make sure a developer's widget is structured all good.
  • Discussed with Corey to see what we should do to wrap up previous work for preflight checks. Main changes from the work previously done include:
    • Preflight checks no longer check the content of the creator/player/score JS files, and only checks that they exist.
    • Preflight checks depend on developers specifying the name of their widget files in install.yaml (files.player, files.creator, score.score_screen). Appropriately, webpack.config.js must be configured to output widget files using those same names.
    • Changed up the styling and layout of the preflight checks in the UI (see below).
    • Checking logic was slightly modified to be a bit smarter, informing the user what exact issues had occurred. Brief descriptions are given in the UI and more detailed descriptions are listed in the dev console.
    • Widgets can be downloaded/installed regardless if all preflight checks pass or not now. This should help in cases where developers want to test their widget in a local install of Materia, but may not have all screenshots set up, or what not.
• Fixes Add a mechanism to scrape through a qset and verify that a 'question' structure is present. #26 - The demo qset is scraped to see if a question structure exists. This is a part of the preflight checks above.
• Fixed Add an install.yaml validator #7 - install.yaml is validated as part of the preflight checks above.
• Alert dialogs now show up again. Previously, a custom CSS rule was put in place to prevent a login timeout alert from showing up. This however prevents any alert dialog from showing up, including those sent by the widget when attempting to save. With the custom CSS removed, I don't seem to be getting any login timeouts anyway (but maybe some more testing/poking around is needed).
  • EDIT: I found out that a network timeout dialog pops up when you terminate the MWDK webpack server in the terminal. Personally, I don't think there is any case where I'd want to continue using the site when the server is terminated (since most things wouldn't load anything), but it's up for debate.
• MWDK now checks for the presence of either webpack.config.js or webpack.config.cjs when initializing. This allows the easy use of an explicitly-defined CommonJS webpack config, saving some headaches when your project is using "type": "module" (like Pyramid Game is)

The only thing not addressed in the original issue is #21, or any of the 'qset editor' or 'install.yaml editor's mentioned in any of the other issues