240 convert event model to use dls python skeleton

[evalott100]

Closes #240

Converts event-model to use the DLS python skeleton, adding all the features other than the .vscode and the container, the following have been added:

• using a single pyproject.toml instead of requirements.txt and requirements-dev.txt
• black
• isort
• having the git version generated by setup.py instead of versioneer
• mypy
• pre-commit

The CI has been tested, and will fail only on flake8 and mypy since the master branch __init__.py does not yet have typing support.

This change will introduce to event-model the older commits to the DLS python skeleton - those which altered features which will be included in this PR.

[coretl]

Suggest it would be a good time to make a bluesky version of python3-pip-skeleton. The steps:

• Fork DiamondLightSource/python3-pip-skeleton to bluesky
• Remove VSCode and container bits of it and docs that ref (as per above comments), and change the updating-tools.rst to point to the bluesky org
• Change python3-pip-skeleton-cli to be able to get it's skeleton from a different org (still called python3-pip-skeleton)
• Make another branch starting from event-model main and adopt bluesky/python3-pip-skeleton into it
• Apply the review comments I made above

[evalott100]

@danielballan Pretty much good to go I think, let me know the answers to Tom's questions in the unresolved conversations and I'll make changes :slightly_smiling_face:

[evalott100]

Had to close since we'll use a new branch with the bluesky skeleton adoption.

[danielballan]

@coretl asked some questions related to this PR via DM. I'll consolidate them here:

do we still need to test against different jsonschema versions?

Yes, as long as it's not too much trouble. Pip dependency resolution frequently gave us an older version that created troubles, not that long ago.

do you use numpy style everywhere?

Yes, that is the standard throughout Bluesky projects.

did I get the RST title underline style right?

Yep!