Add organization logos to groups menu

Resolve relative URLs when getting PDF URL from PDF.js

If PDF.js is launched with a `file` query-string parameter that is a
relative URL, then `window.PDFViewerApplication.url` will be that
relative URL.

When capturing the metadata from the PDF in order to search for
annotations or find relevant groups, we want to use an absolute URL.
This commit uses the existing `normalizeURI` helper to resolve the
possibly-relative URL.

Fixes https://github.com/hypothesis/product-backlog/issues/579

Extract the existing `normalizeURI` function from guest.coffee into a
utility module and re-use it in document.coffee to convert relative URLs
to absolute ones.

Also implement some direct tests for this function.

Extract `createStore` helper out of `store` service

Replace "inherits" package with ES 2015 class inheritance

Convert Adder to an ES2015 class

Remove the need to alias the `Adder` instance to `self` by using
arrow-functions.

This commit and the next few refactor `Adder` to a "proper" class for
easier readability.

Add `expand` param to all groups.list requests

Minor bug fix

Replace use of "inherits" package to create classes that derive from
`EventEmitter` with ES 2015 `class Foo extends EventEmitter` syntax, for
readability.

This method is part of the Redux store API so we don't need to test it
in detail, but this is additional verification that `createStore`
returns a working Redux store.

Move date, time & retry utility code to `util/` dir

Pdf subframe annotation

As per #648, move several modules containing utility functions which
have no dependencies on other code to `src/sidebar/util`.

The `thunk` middleware is used by the `annotations` module and likely
others in future. Rather than require it to be passed to `createStore`
in each test that uses it, I think it makes sense to always include it
as the standard way to handle async/non-pure actions in the client.

This functionality is now covered by tests for the `createStore` helper.

The `store` factory function contains some useful logic for composing a
store out of a set of _modules_ which handle different parts of the
application state, exposing the actions and selectors from each module
as methods on the store.

To facilitate re-use of this logic in tests and to make it easier to
test this logic directly, extract it out of the `store` function into a
separate `createStore` helper.

Doing this enables removal of `modules/index.js` which existed to
combine parts of the modules together.

Rename "annotationUI" => "store"