Redirect rules aren't configurable

[imurray]

I've given the extension a pretty generic name, with the intention that it could be used by various people with custom redirect rules. However, the only current mechanism to edit the rule list is to edit the source code. I've pushed the extension out as it is now because it does what I want, and others might still find it useful. However, if a bunch of people end up using the extension, it should probably be made configurable.

[imurray]

Given #3, maybe I won't make the extension too powerful — at least not in the near future. Some configuration options might still be nice, but maybe not the core list of rules. For now I'll prefer new rules as pull requests, so everyone benefits from the new rules.

[imurray]

I think optional permissions could be used, so that users agree to allow access to more hosts when they enable rules.

The list of rules is already quite unwieldy, such that it's not always possible to see a complete list of the hosts when agreeing to permissions. Making most of the rules optional, with the ability to agree to permissions later, seems like a good idea. I hope to return to this idea, after the refactor required to support Manifest V3 for future versions of chrome (see manifest3 branch).