Limestone rewrite

[Nealium104]

Related to this exploreuk-web-app PR, this pull request is a full UI rewrite of the findingaid. This rewrite is primarily for addressing accessibility concerns.

This PR fixes #7, fixes #8, fixes #9, fixes #10, fixes #22, fixes #24, fixes #33, fixes #34, fixes #35,

[nrsa222]

To do:

• Related to Insufficient color contrast on FA request buttons #9 and Color contrast on select button #35 - Once the button is selected the hover color remains.
• Objects were removed from accordions, but we've decided to temporarily revert change for visual context. Accordion style - https://patternlab.uky.edu/?p=components-zipper-slab, https://patternlab.uky.edu/?p=molecules-zipper
• Empty divs are nested under every class="fa-component"
• "Requests" block is missing option to remove items
• "Requests" block buttons need style cleanup
• "More from this collection" link in TOC is broken
• General cleanup of development helpers and duplicated code, can also remove unused code

[nrsa222]

Fixes #57

[Nealium104]

My last two commits need some explanation.

Accordions

Limestone's accordion components weren't made with the idea that they might be used as nested components, so the js file for jquery-accessible-accordion.js needed to be patched to force controls on only the top level of an expansion/collapse.

While I would prefer making a PR to the original source, it is an MIT license, and there would be multiple steps of approvals to get to production. I've added the file to the repo and then committed my patches in a separate commit for any future reader.

CSS loading/layers

During the CSS work, I got a bit frustrated with the specificity wars between limestone and extra.css, so I read a bit into css layers. Extra.css now imports limestone into its own layer, meaning that all unlayered styles in extra.css now win any conflicting rules, regardless of specificity. All overrides (things that limestone designates as !important) will need to be in the overrides layer due to how !important works in layers.

To accomodate the above change, limestone is now loaded with preload and imported in the extra.css file. The preload would normally cause a flash-of-unstyled-content, but the import rule forces render blocking.