Add a test for user API

[allenporter]

This test currently fails

[chemelli74]

Tests are created as sync and not async so we need for now to pin aiohttp to a old version

[allenporter]

The response parsing works fine:

INFO     root:rest.py:163 response body: {"user": {"encodedId": "some-profile-id", "locale": "en_US", "fullName": "Full name", "displayName": "Display name", "displayNameSetting": "name", "firstName": "First", "lastName": "Last"}}

The issue I was explaining over discord is

fitbit-web-api/fitbit_web_api/api/user_api.py

Line 196 in a5329e7

response_type=None, # noqa: E501

) is setting response_type=None which means that the API client returns None

fitbit-web-api/fitbit_web_api/api_client.py

Line 175 in a5329e7

return_data = None

and as I was saying this is consistent with the response data models not being produced https://github.com/chemelli74/fitbit-web-api/tree/main/fitbit_web_api/models and the return type in the documentation being None https://github.com/chemelli74/fitbit-web-api/blob/main/docs/UserApi.md#return-type-1

This is all repeating what I said on discord, because the fitibt openapi spec itself does not include these.