style: isort and black code styling

KNOWN_ISSUES.md

@@ -24,4 +24,4 @@ here so we can track them and remove when fixed on EV side
 
 - The API does not offer a simple way to ensure that a custom field is set to a certain value for member. You have to either create (POST) a member_custom_field if the member has no relation to a certain custom field yet, or modify an existing one (PATCH) if there is such a relation. Before modifying a value you therefore have to know if such a relation exists or not.
 - When deleting a custom field, the relation between the member and a custom field still stays intact, just with `customField` set to `None`. The tests therefore manually delete member custom field associations before deleting the actual custom field definition to not pollute the test tenant.
-- Apparently "path" doesn't mean, that is always will be a HTTP URL. In some cases it has been reported that the path is a local file path, following the `<member_number>_<firstname>_<lastname>/<random_number>_<member_number>-SEPA-Mandat_,,,` syntax. My assumption is that those paths have been used before the introduction of S3 storage on EV side. As I couldn't find any documentation around the naming standard, nor find any information how to actually work with these fields, we're simply adding a string fallback.
+- Apparently "path" doesn't mean, that is always will be a HTTP URL. In some cases it has been reported that the path is a local file path, following the `<member_number>_<firstname>_<lastname>/<random_number>_<member_number>-SEPA-Mandat_,,,` syntax. My assumption is that those paths have been used before the introduction of S3 storage on EV side. As I couldn't find any documentation around the naming standard, nor find any information how to actually work with these fields, we're simply adding a string fallback.

easyverein/models/base.py

@@ -1,7 +1,7 @@
 from pydantic import Field, PositiveInt
 
-from .mixins.empty_strings_mixin import EmptyStringsToNone
 from ..core.types import DateTime, EasyVereinReference
+from .mixins.empty_strings_mixin import EmptyStringsToNone
 
 
 class EasyVereinBase(EmptyStringsToNone):

easyverein/models/contact_details.py

@@ -5,11 +5,11 @@
 
 from typing import Any, Literal
 
-from pydantic import Field, EmailStr
+from pydantic import EmailStr, Field
 
+from ..core.types import Date, DateTime
 from .base import EasyVereinBase
 from .mixins.required_attributes import required_mixin
-from ..core.types import Date, DateTime
 
 
 class ContactDetails(EasyVereinBase):

easyverein/models/member.py

@@ -7,9 +7,9 @@
 
 from pydantic import Field, PositiveInt
 
+from ..core.types import AnyHttpURL, Date, DateTime, EasyVereinReference
 from .base import EasyVereinBase
 from .mixins.required_attributes import required_mixin
-from ..core.types import AnyHttpURL, Date, DateTime, EasyVereinReference
 
 
 class Member(EasyVereinBase):