Tags

* Ability to post an event with a different timestamp than now. Contribution in !56 by @alasheen.

* Move to pyproject.toml, and refine the docs

* Allow passing a list of tag names to the get_events methods

* Ensure that the codebase is correctly typed
* Add __len__ to the paginated objects
* Freeze the paginated objects
* Fix a few typos in the docs

* Support pyrbac v1 Token types

* When adding an attachment of a file of an indeterminable mime type, according to the ``mimetypes`` library, an exception is raised.
    * Future work to support this case is possible. Please get in contact if you need the behaviour to handle indeterminable mime filet types. (ref https://gitlab.cern.ch/scripting-tools/pylogbook/-/merge_requests/44#note_6323954)
 * The package is now marked as typed, enabling an improved experience when type-checking your own code against pylogbook. Thanks to @nmadysa for his contribution (!44).
 * The package has been updated to conform to modern coding standards, ensuring a more consistent style. This is checked systematically with pre-commit (!46).
 * Use the Acc-Py v2 gitlab templates

* Ability to include tags in newly created events when calling Client.add_event (with thanks to @clombard and @simonp for their input)

* Ability to authenticate with bearer tokens (e.g. OIDC) as well as RBAC tokens
* Improved error handling, especially in the case of invalid authentication
* Access to the tags of an event, and an API to list all tags on the server
  * Further work is planned to allow tagging of newly created events, and updating existing ones
* Fix the named logbook enum item for "LINAC_4"

* Add support for bytes as well as strings being passed to ``Event.attach_content``

* Allow ``ActivitiesClient.activities`` to be get and set/updated

* Added ``Client.rbac_b64_token`` to allow getting and setting of the base64 encoded RBAC token string. It is also possible to set the token using a PyRBAC token instance (in the constructors or in the ``rbac_b64_token`` property setter).

* Complete re-write of PyLogbook to use the new logbook API featuring a high-level object oriented API for ease of use

* Upgrade to the latest Java logbook interface, which now handles both old and new logbook versions
* v2 is moving to maintenance mode - the future pylogbook, v3, will be based on the logbook REST API

* Improve the README
* Use the new registration mechanism from cmmnbuild-dep-manager to allow wheels to be published
* Automatic versioning through ``setuptools_scm[toml]``