Rework Tags plugin

This PR reworks the Tags plugin and introduces the Widget extensions concept.
- Widget extensions are functions that can be added to a widget as options.extensions (expects a list)
- These functions are run on the widget at rendering.
- This is a hook point to customize widgets, add necessarily new fields, etc.

The Tags plugin:
- Converted from coffee to js.
- It is no longer a plugin but an UI extension, so moved from plugins directory, to ui directory
- The filtering part is gone, since we have a separate plugin for that
- Offers two widget extensions: `configureViewer` and `configureEditor`

Even looking at this code I have to think really hard about several things to understand what's happening.

Is `extension(this)` supposed to be calling a constructor, such as `UI.Tags`? If so, why doesn't it use `new`? If we're passing `this`, why doesn't the `Tags` constructor take a widget as its first argument?

Something smells really awful here. :hankey: