Improvements to ui/config

[quisquous]

There's a number of things I deliberately chose not to do as a part of the initial version of the config UI that I pushed off until later but I think would be really good to do.

• save collapsed/uncollapsed state in browser storage (currently everything resets when you reload, which might be irritating)
• support for some option type that is a table/object (for nicknames, custom mobs, pullcounter, etc)
• add nickname support
• it'd be easy to add duration overrides for triggers
• (maybe) condition overrides for triggers (this could be complicated in some cases)
• when setting data in the savedConfig, maybe just delete it if it's the default, vs having an explicit "this value is the default" saved there
• convert pullcounter to be stored in options, so that it can be edited via ui/config

Things that I am not sure should be done:

• custom triggers should just be done in JavaScript, in my opinion
• I am not sure about custom trigger output, as this is very complicated for triggers that have a function vs a literal object as a return value

[quisquous]

I think it could be possible to warn users that they have options in user files that are overwriting (and changing) values in their config settings. This might get noisy, but maybe it'd be worth it?

[Akurosia]

could we somehoe fix the ordering for content in e.g. Raidboss > ARR Trigger ? it dirves me nuts that it has T1 followed by T10 etc

[quisquous]

Probably also the config ui needs a "reset to defaults" button (with some "did you really mean this??" so that folks don't hit it accidentally).