This adds keystone v2 and v3 tests to the charm.
However, because of bug#1611393 the tests can't execute test 400 which
would check the API to barbican. Thus, it is disabled and the tests
only check that the relation is set up properly.
Working charm with unit tests. Various features:
Change the install ownership for token store
It turns out that the 'user' that creates the token store, is the only one that
can access it, apart from root. As Barbican uses a 'barbican' user for the
barbican-worker process, we need to create the token store with 1777 perms (see
https://github.com/opendnssec/SoftHSMv2/issues/185) and also create the initial
token using the barbican user.
Add an initial README.md: This describes the charm, where to get help
and how to use it.