"Pythonic" field naming

[mo-lukecarr]

Could we use Pydantic's field aliases to use "Pythonic" field names (i.e. snake case) in the models, without losing the compatibility of validating and serialising the EDR specification?

This work might be blocked by the fact that Pydantic currently requires you to explicitly pass by_alias=True when dumping a model instance. There doesn't appear to be a way of automatically enabling by_alias, such as through a model's ConfigDict.

If we were to implement this change and introduce aliases, we'd probably need to have a way of defaulting to validating and serialising by alias (otherwise the library would rely on users to remember to always pass by_alias=True).