Have the Meilisearch API Key stored in the main site's database #2

At the moment, the API key is hard-coded. This was okay during the initial stages of the site's development (which hadn't reached '1.0' yet). With that said, it was something I just forget to change and I didn't stumble across it until the site's first deployment. I was so comfortable with the dev. environment just working I forgot about how it would need to change in the production environment.

Anyway...

This function (in search.lisp) needs to call out to nera.lisp and grab the API key from there. That means the site-settings model will need updating, as well.

At this moment in time, the JavaScript files have hard-coded versions of the API Keys:

But they will need they keys dynamically added like the server URL here (as part of the site-settings model passed to the Djula template).

At the time of writing, I'm unsure on how to track this. Should I put it as a check-list here? Or, break out each task into its own issue and track them individually? I'm going to finish creating this issue and come back to how to track it later.