We've encountered an issue related to two-factor authentication cookie validation after a major Django version upgrade, as detailed in issue [#686](https://github.com/jazzband/django-two-factor-auth/issues/686). This issue arises due to the change in user password hashes when Django's hash iteration count is updated in a new version, leading to a mismatch in the two-factor authentication cookies' validation.

We can for now implement a workaround. This involves catching the `BadSignature` exception raised during the cookie validation process when there's a mismatch in the hashes. This situation occurs after upgrading Django, which causes the user's password hash to change, thereby invalidating the existing two-factor authentication cookies.

This issue is critical for us to upgrade our Django version without disrupting the user experience of people coming back and having a 2FA cookie.

posthog/api/authentication.py
token = serializers.CharField(write_only=True)
    password = serializers.CharField(write_only=True)
    def create(self, validated_data):
        
        if settings.E2E_TESTING and validated_data["token"] == "e2e_test_token":
            return True
        try:
            user = User.objects.filter(is_active=True).get(uuid=self.context["view"].kwargs["user_uuid"])
        except User.DoesNotExist:
            raise serializers.ValidationError(
                {"token": ["This reset token is invalid or has expired."]},
                code="invalid_token",
            )
        if not password_reset_token_generator.check_token(user, validated_data["token"]):
            raise serializers.ValidationError(