Raise OperationalError for socket timeouts

[jiezhen-chen]

Map socket timeout errors to OperationalError instead of InterfaceError

Description

socket.timeouts are a subclass within socket.error, and socket.error is classified as InterfaceError. Hence socket.timeouts gets classified as InterfaceError as well. This change will map socket.timeouts alone to OperationalError, where other exceptions within socket.errors will remain unchanged.

Motivation and Context

This PR resolves this issue

Testing

Conducted manual testing - hit timeout and received the below error message:

    raise OperationalError("connection time out", e)
redshift_connector.error.OperationalError: ('connection time out', TimeoutError(60, 'Operation timed out'))

Added unit test and integration test as well.

Screenshots (if appropriate)

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)

Checklist

• [x] Local run of ./build.sh succeeds
• [x] Code changes have been run against the repository's pre-commit hooks
• [x] Commit messages follow Conventional Commit Specification
• [x] I have read the README document
• [x] I have added tests to cover my changes
• [x] I have run all unit tests using pytest test/unit and they are passing.
  • By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[Brooke-white]

@jiezhen-chen -- testing looks good, no regressions. if you could run the repo pre-commit hooks on this change I will go ahead and merge it