Allow users to whitelist hosts from the option page

[cschanaj]

This PR will:

• Add UI to add disabled site without require a first visit (close Add ability to disable HTTPS Everywhere for specific domains without first visiting the site #17434)
• Add wildcard support for disabled site (close Allow end user to add *.neverssl.com into the disabled sites list #18503)
• Allow us to get rid of the double-negation toggle (follow-up Ignore loopback and private network addresses (such as 192.168.0.1) #18565 Make HTTPS Everywhere always ON by default #18590)

Note that:

• this PR have temporarily removed the unit test for the nullIterable object because some refactoring works are blocked by Add unit tests for util.js #18563. I will submit a PR to restore the unit test once that is merged. See 8a6bace

• wildcard matching in this PR is not really working with WASM enabled because of WASM implementation sometimes fails to find rules #18589. So the review of this PR will be much easier with the fix in Fix WASM wildcard rules handling issue https-everywhere-lib-core#1 merged.

P.S. Personally, I hope this can be merged before a release is made (#18618) if it is not too urgent.

EDIT: Updated the incorrect PR reference.

[pipboy96]

Good idea, makes more sense IMO.

[cschanaj]

@zoracon would you take a look at this PR as well?

[zoracon]

Reviewing today

[pipboy96]

I think it would also make sense to allow the user to remove temporary exclusions created by "Open insecure page for this session only" option on EASE error page.

[zoracon]

This mostly looks good to go, but just one comment for url validation

[cschanaj]

wildcard matching in this PR is not really working with WASM enabled because of #18589. So the review of this PR will be much easier with the fix in EFForg/https-everywhere-lib-core#1 merged.

I am so sorry that I was wrong on this statement. It seems there is uncommited changes on my local branch and the wildcard matching (for disabled sites) is not working because the refactoring work was partially done.

[cschanaj]

@zoracon @pipboy96 this is ready for a second round of reviews. thanks.

[cschanaj]

ping @zoracon for a second review. thanks.

[zoracon]

Pulling this down and testing today. Apologies for the delay

[pipboy96]

@zoracon I think we should also allow adding whitelisted domains/disabled rulesets and maybe force/disable EASE from managed storage (enterprise policy). I want to try implementing this.

[zoracon]

This is something we can push in for now, I will use this moment to also do a "what was updated" page for users who update so they know this feature is available