Define JSON enconding to UTF-8

[by3nrique]

Pull Request Summary:

The current implementation of response.json() from the requests module involves time-consuming charset detection, particularly problematic when handling a large number of requests. (For more details, see this Stack Overflow discussion: Stack Overflow - Performance Issues When Formatting Using JSON).

This pull request introduces an enhancement to the dicomweb-client module, specifying the character set and bypass charset detection. This improvement can significantly boost performance. This is compatibledwith the requests module (https://docs.python-requests.org/en/latest/user/quickstart/#response-content)

In the specific case of DICOMWEB, the presence of the UTF-8 charset in every response is guaranteed, as dictated by the DICOM standard. More information about this requirement can be found in the DICOM standard documentation: DICOM Standard - Section F.2.

Changes:

• Enhanced the dicomweb-client module, specifying the character set.
• Improved performance when dealing with a high volume of requests.
• Assured UTF-8 charset in DICOMWEB responses as per the DICOM standard.

Testing:

All tests have passed successfully.

Notes:

Thank you for your attention to this matter.

[pieper]

The change sounds fine to me. Not sure why the CI is failing. Any comments from @hackermd @cgorman or others?

[cgorman]

@pieper Ah yes numpy deprecated a method name so mypy is failing. I actually opened a PR to fix it #86 back in July but wasn't able to merge due to review requirements and then I forgot about it. Would you be able to approve it and see if we can get it merged? That should let us merge this as well.

[pieper]

Thanks @cgorman , I merged it.

@by3nrique would you be able to rebase to the current main so that the CI tests will run again?

[by3nrique]

Thanks @pieper. I have rebased to the current main, then there should be no problem.

[cgorman]

Looks good to me, thanks!