Report host for invalid tokens

[DavidStirling]

An issue with the current get command is that if your token expires it's not immediately obvious which server that token was for.

To solve this I've modified the error message to include the server name.

Before:

> omero_user_token get
ERROR: Token is invalid!

After:

> omero_user_token get
ERROR: Token for my.omero.server is invalid!

Also fixed a typo in the setter message

[sbesson]

omero@search-test:~$ omero_user_token get
ERROR: Token is invalid!
omero@search-test:~$ pip install omero_user_token-0.3.0.post1.dev28154048-py2.py3-none-any.whl 
...
Successfully installed omero-user-token-0.3.0.post1.dev28154048

[notice] A new release of pip is available: 23.3.1 -> 25.0
[notice] To update, run: pip install --upgrade pip
omero@search-test:~$ omero_user_token get
ERROR: Token for localhost is invalid!

Looks good. Should we aim to get this released as 0.1.2 ?

Note this package needs a bit of modernisation in terms of build and I should probably adjust #8 accordingly. At minimum, should we remove setup.cfg so that we don't create wheels that pretend they are Python 2 compatible for the patch release?

[DavidStirling]

Thanks @sbesson, a release isn't essential but it's probably worth trying to integrate #8. As that PR also adds support for custom token directories I'd suggest that we handle modernising the setup/actions scripts in it's own PR after getting that merged.

[sbesson]

Thanks @DavidStirling. I'll get this in and assign you to the review of #8. Then we can look into updating the build system before a release