To ensure we have complete and accurate types, using strict mode and not
ignoring missing imports is helpful.

pre-commit runs mypy in an isolated environment without access to the
project's dependencies. In order to typecheck the code in the same way
as mypy running from the project's environment, it needs to have access
to the project's dependencies. Without changing the hook to install them
via poetry, the only way to do this is to export the dep list from
poetry and hard-code the hook with them.

We're getting a type error when using pydantic methods on the pydantic
CloudEvent model. We can avoid this by using conversion.to_dict()
instead of the model_dump() method. Also, this seems more reliable, as
the pydantic serialization from model_dump() is not JSON compatible
without `model_dump(mode='json')`, and even then it may vary from the
way CloudEvent expects.

I've been reading through ucam_fass in conjunction with the IAM Account
Selector project, and adding types as an exercise in better
understanding it. Seems like it should be useful for users of the module
to have types available.

MyPy was treating it as not a subtype of pydantic.BaseModel, so it
didn't have Pydantic model methods. This seems to be caused by
differences between pydantic.BaseModel and cloudevents.pydantic.v1 /
cloudevents.pydantic.v2 compatibility imports. Making the type look like
it's always from v2 solves the type confusion/error.

When event handlers raise exceptions other than UCAMFAASException, we
now include the exception details in the
"function_failed_uncaught_exception" log error event.

This resolves a FIXME comment in the code.

Type annotations and exception traceback logging.

`test_example_raw_event()` was calling a `@raw_event` handler with a
dict, but raw_event handlers receive bytes (the raw HTTP request body).

Add type annotations & minor groundwork for #19

See merge request !24

chore: Configure Renovate

See merge request !19

chore: add webhook proxy architecture decision record

See merge request !35

Tests running locally (although not in CI/CD) were broken, due to
updates to the Dockerfile not being captured in the docker-compose
configuration as well.

Also changed user to root for running tox. This is required to allow tox
to install dependencies into the tox environments, which are mounted as
volumes when tox runs locally.

Issue 16: Add release it to handle version bumps

Closes #16

See merge request !36

fix: rename release-it.json to .release-it.json

See merge request !37