It is easy to erroneously add extra white space to a text file. For example when writing with an editor like `nano` or when using `echo` without the `-n` argument.

Handing that white space over to python-challenge-bypass-ristretto's `decode_base64()` method will make it fail in a rather opaque way, see https://github.com/LeastAuthority/python-challenge-bypass-ristretto/issues/37.

This eliminates white space including newlines around the key expected to be in that file.

The redeemer will submit this many tokens with its redemption request now.  It
needs to agree with whatever the issuer wants to do, of course.

If SpendingController develops some internal state it should really remain
internal, anyway.  Don't make _plugin.py worry about this.

just bumping CI really

Instead of immediately extracting passes, get them and later mark up the store
with the outcome of the attempt to use them.

This removes almost all uses of the global value.  All that remains is its use
as a default in case no configuration is given.

This way, it can be an empty list.

The first time the node starts there will be no rootcap and there cannot
easily be one unless the node is allowed to start so one can be created.

And a corresponding `created` field to the voucher model object which
propagates to the web view.

We do so by introducing a limitation that the client must be configured with
an issuer and it must match the issuer announced by any storage server the
client is to talk to.

The client will decline to speak to any storage server without a matching
issuer.

Although ... the client resource doesn't really the part of the redeemer that
needs the announcement.  Maybe that part of the redeemer belongs somewhere
else.  Probably.

lots of mess to clean up though

Passes cannot be constructed until we know how we're going to use them since
they are derived from the unblinded tokens and an operation-specific message.