[Python] Consider to raise or normalize if a timezone aware datetime.time object is encountered during conversion

Python datetime.time objects may have timezone information attached, but since the time types (type32 and type64) don't have that property in arrow we simply ignore it.

We should either raise an error or normalize to UTC.

**Reporter**: [Krisztian Szucs](https://issues.apache.org/jira/browse/ARROW-10004) / @kszucs
#### Related issues:
- [[C++][Python] Refactor python to arrow conversions based on a reusable conversion API ](https://github.com/apache/arrow/issues/26017) (relates to)

_{**Note**: *This issue was originally created as [ARROW-10004](https://issues.apache.org/jira/browse/ARROW-10004). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

Start at the Python conversion path for datetime.time objects and inspect existing tests for timezone-aware values. Decide whether the conversion should raise or normalize to UTC, then add coverage that confirms the chosen behavior and preserves handling of timezone-naive values.

Written by the indexing model from the issue text.