I changed most of the logger statements to use a class attribute, in
this way it's easier to identify which class it's logging them.

in some cases I leave a module-level logger, when we're either using
functions or when the module it's too small.

at the same time I did a general review and cleanup of the logging
statements.

The offline toggle added a race condition in which the client could end
up offline forever. We decided to remove it for now and then decide if
soledad client needs to know about network connectivity (check:
https://0xacab.org/leap/soledad/issues/8789).

- Resolves: #8721

Check if a new fetched key was signed by a old key with the same address.

Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150

- Resolves #8112

the token is set when we get the srp token in the keymanager service,
but it wasn't been propagated properly to the internal nicknym object
that was refactored recently.

here I make the setter write the same token to both keymanager itself
and the nicknym.

some little additional refactors:

- move gpg initialization to a helper method
  in this way it becomes easier to stub the soledad and keymanager
  components, for testing.

- name nicknym token as publicly visible, since i'm accessing
  it from the keymanager object.

- Resolves: #8651

- some pep8 problems
- some confusion with old and new code after merging
from old keymanager

disabled some tests that were failing, for some reason the twisted
logger doesn't want to be patched?

besides, I don't think it's a good idea to rely on log information for
tests. what is it really that we were trying to test there?