Simplify code paths related to Bramble API methods, events and preferences

[humphd]

We have lots of features that are basically implemented the same way, and it's always a very manual process (e.g., #584).

It would be interesting to see how much we could do to automate this kind of code, such that adding a new preference is as simple as instantiating a new Object from a constructor, which does all the manual steps for you automatically.

If someone wants to work on this, I'll help figure what this should look like.

[humphd]

See also #595

[Pomax]

I read through these bugs but I'm not super clear on what part(s) can be turned into encapsulated functionality that is easy to run in an automated fashion. Can you elaborate on what thoughts you have here?