Allow loadout naming

[NickKoester]

Allows users to change the name of their loadouts . When a loadout is created from a preset it will use that name as the default instead of "Loadout n".

closes #146
Also could be an enabler for #217

[LlemonDuck]

Thanks for the PR. We've been having discussions moreso on whether we should implement this, rather than how, but it's nice to have this work done for us if we ultimately accept it 😄

We'll get back to you with a response soon.

[jayktaylor]

Thanks for the PR.

I think we're willing to support this, given that the UI you have created is reasonably minimal.

I've committed an adjustment to your code which removes the tick and cross buttons, and instead has a simple flow where clicking on the pencil (which I've made slightly smaller, to be less jarring) focuses your input on the text box, and then you can type a name and hit Enter or click away from the element to save. I think this is a simpler and easier to understand UX.

Additional feedback:

• When you load an existing shortlink (AKA one created before this PR) with multiple loadouts in it, each loadout except the first has an empty string for loadout.name. This should be changed (probably in state.tsx where we import the data) so that loadouts with a missing name key are named after the array index.
• Do we want to set a reasonable character limit for loadout names? My feeling is yes, maybe 24 characters max.
• Do we want to show the loadout name in the results table? I think we do, but how are we going to make it look good with a longer name? Do we wrap the line like below, with a small line-height? Do we truncate (probably not, imo)?

[NickKoester]

• Set default name if using old shared loadouts
• Set max input length of 24 characters
• Added loadout names to results table

[jayktaylor]

We moved some stuff around with branches. The base branch for the repo (and PRs) is now staging. We'd already merged this PR into that branch, but GitHub is confused by the history so won't let me change the base branch of this PR.

I'm going to close this PR, but your changes were merged in d652498. It will go out to the production site in our next deployment (along with the reverse DPS, etc changes in the staging branch). You can test here.