fix: proper handling of 'na' values

[YpeZ]

What are the main changes you did:

• changed the way pandas handles 'na' values when creating a DataFrame from either a csv or list/dict data
• the values 'NA', 'na', 'Na' are now processed as they are
• actual not available values are stored as empty strings
• float and int values are not affected
• additionally, the handling of errors in request responses is improved by including more checks in the _validate_graphql_response method

how to test:

• the dev script now includes an extra pet that is saved (and deleted) in a schema in the save_schema tests, named 'NA' with status numpy.nan. You can verify that the name is stored as 'NA', and the status is left empty

todo:

• updated docs in case of new feature
• added/updated tests
• added/updated testplan to include a test for this fix, including ref to bug using # notation

[davidruvolo51]

Looks good. There are a couple of linting issues flagged by pylance, but everything works as expected.

[davidruvolo51]

Should isinstance be used here instead?

https://pylint.readthedocs.io/en/latest/user_guide/messages/convention/unidiomatic-typecheck.html

[davidruvolo51]

Pylance also flags this block as unreachable.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[davidruvolo51]

Looks good!