Meta: disable features with a click in the options

[fregante]

Closes #2040

Outdated notes

Notes:

• I had initially had the link on the feature name, but a bunch of blue links looked tacky.
• I thought we could handle this with an autocomplete-like feature, but with that we can't also link to the source (this would probably be solved if we had descriptions in each file)
• about "checked means disabled": this is because the features are enabled by default, but to show them as "checked means enabled" we'd have to specify them all in the defaults in background.js.
  
  The form could be made more understandable by using colors, i.e. green on unchecked and red on checked boxes. Edit: I think the strikethrough is clear

screenshot of bdea47d (outdated)

[fregante]

Also looks good in Firefox:

[fregante]

Moved description to second line, added screenshots field.

[fregante]

a way to quickly collapse the Feature list in options to easily get to the Custom CSS option.

We could move it to a tab, but I'd like to keep the options as "flat" as possible, also so we don't have to care much for their styles (given that it's shared between Chrome and Firefox)

You could also just move the custom CSS box above the feature list

Yeah, I like this better. I left the "logging" toggle below the list because it's more of a development feature anyway.

you could also add the descriptions as tooltips instead

Not tooltips because descriptions are long and sometimes include code, but I wouldn't mind moving the description behind an expand button. However I dislike having a long list of expandable micro information.

I'd hide the feature name too, but it gives users a handle to remember, discuss and find.

[simonkotwicz]

This is out of the scope for this PR but here are some other thoughts I had:

• Group features in the same way they are grouped in the README (Declutter, More actions, etc.). However, this would require extra information to be added to each feature and maybe some feature don't fit in those categories.
• Mark new features with a different colour or "NEW" tag (or bring them to the top of the list under a "New" heading) until the user clicks on the feature/source/screenshot.

[fregante]

I need to work on this further because the migrations aren't being triggered at times, I suspect it's because setTimeout in options-storage makes webext-options-sync call chrome.runtime.onInstalled too late.

I think the solution is to extract the features list at build time.