Create run-locally.sh to automate running locally, fix last commit, add name to Lint workflow

[hahayupgit]

Enables users to run locally with 1 script. Script MUST be ran from .../whisky-book, or will not work. Script can be ran either ./scripts/run-locally.sh to generate the sidebar, check linting, and open the page, or ./scripts/run-locally.sh -i to install the cargo dependencies, and then do the same thing as ./scripts/run-locally.sh.

Also fixes the repository that mdbook-last-changed was pointing to, as it was previously the Whisky repo.

Add name Check Linting to linting workflow

[JoshuaBrest]

I'm not really happy with these type of scripts. Here's why:

1. Script should never install packages for the user even if they user ask for it.
2. You shouldn't be checking if the base path is equal to whisky-book. This is because the user can clone into different directories.
3. The script is kind of unnecessary. There's not really a purpose of running both generate and the lint tool at the same time it gives us a false sense of security that the sidebar is automatically generated.

[hahayupgit]

Why shouldn't scripts install packages even if they ask for it? Genuinely curious.

I check if the base path is equal to whisky-book as mdbook serve --open only works in the root directory of whisky-book.

I personally like the script as I prefer one command to both generate the sidebar and open the book, though that's just me. I'm curious what you mean by "false sense of security" though. Would the generate.mjs script not throw errors if it was improperly generated?

[hahayupgit]

Talked on Discord, I'm gonna close this for now and open another with the smaller changes, and re-implement the script later!