Centralize configuration and store all inputs in local storage and the uri

[cass-kazumori]

Fixes #44 Fixes #47

This:

• Brings in Zod for data validation and sanitization.
• Removes handling of defaults from the Book class and HTML.
• Centralizes configuration handling and moves form validation and decision making around defaults to a unified model.
• Begins storing all inputs within local storage.
• Begins storing and syncing all inputs with the uri. Loads this state, if present and with precedence over local storage, when the page is loaded. When no configuration exists within local storage or the uri, it loads a model-adherent configuration set with all default settings.
• Updates the event listener to listen to changes across any input: now including checkboxes and radio buttons.
• Updates the form render handling to manage all inputs, not just a few specific ones. This lets the form be kept in sync with the settings.
• Updates the ZIP export process to include a static link to the imposer in the bundle, holding the state of the site at time of impose. I'm fine updating the exported file name to w/e we want to.
• Fixes all previously broken tests. (Anyone want me to add a GHA with a test step for CI, to be run on PR here in GH? – acronym hell!)

If we were to want to add a new input or configuration, the proposed process would look similar to the following:

• Update the configuration schema with the new input.
• Update the form-to-configuration map so that the new input can be pulled from the form and moved into the configuration.
• Update the render handling to select the input element and keep it in sync with the configuration.

Ideally, I'd like to automate the last two – but this is a start.

[sithel]

Am getting an error on the console if I select a Wacky layout -> reload page -> upload PDF -> select Standard Signatures

to be fair tho-- I get a (different) error in the console when going through this this flow on released/current version as well

[cass-kazumori]

The issue with the custom dimensions should be fixed now. We may want to clean up some of our handling around the inclusion (or exclusion) of the custom page size option, and how we track and append that to the page size list. Namely, so that we don't need to manage in several places the handful of (order dependent) calls to pull that option into the list, and when we set it. It's not a big deal or anything, but I wouldn't mind cleaning it up a bit.

@momijizukamori I also added the booklet option to the configuration set for our signature formats. You may just make sure that I didn't mess anything up when resolving out the merge conflicts. I don't believe that I did, but a second pair of eyes never hurt anyone.