fix: use timeouts in REST clients

[3dquattro]

There is a problem, that timeout parameter can be set, but not being used in python SDK.

Fix for issue stackitcloud/stackit-sdk-python#3061

[rubenhoenle]

internal comment: check the upstream (https://github.com/OpenAPITools/openapi-generator ) if this should be fixed there also

[github-actions]

This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it.

[cgoetz-inovex]

Did some digging:

• upstream passes the timeout to request: https://github.com/OpenAPITools/openapi-generator/blob/d9dd07aeaca281b7648606e665b2133d1bfe4409/modules/openapi-generator/src/main/resources/python/rest.mustache#L183
• this line was introduced 4 years ago, preceding our copying/adapting of the templates
• our initial commit to this repo, which introduced python SDK generation, seems to based off v7.7.0 of the generator, which passed the timeout
• commit history and issues don't tell the story why this was removed from the templates

Imo the correct fix would be to update the generator and patch the templates again. The template accepts a number or a tuple of numbers for timeout:

        :param _request_timeout: timeout setting for this request. If one
                                 number provided, it will be total request
                                 timeout. It can also be a pair (tuple) of
                                 (connection, read) timeouts.

The tuple case is not handled in this PR.

[cgoetz-inovex]

Just realized that our rest.mustache uses requests instead of upstreams urllib3. So the timeout handling in this PR is correct. Sorry for the noise.

[cgoetz-inovex]

Thanks for your contribution