Add option to return python datetime object with timezone like Search cursor rather than Timestamp

**Is your feature request related to a problem? Please describe.**
Access Hosted Feature layer on 11.5. the datetime fields is returned as a python datetime object via arcpy.da.searchcursor. However, via the api on the same feature I get a time stamp, so I have to convert to compare. Please make the option to return dates as datetime objects wiht timezone info. Also seems like the timestamp adds 1 micro second, I have to trim of the microsecond as well to comare. the data the HFS was created from has no micro seconds, might be a float issue on converting to a timestamp adding a mircosecond

```python
#SC
(datetime.datetime(2026, 2, 2, 18, 37, 24, 1)
#feature.attributes.get(field)
1770057444000
```

**Describe the solution you'd like**
Add an option or key word something like the below. Just seem like it should default to do that as this is python and datetimes are the preferred option in pythong over timestamp and this change woudl match the currect search cursor. I assume there is a part of the code converting it to a timestamp.
Example.
target_features = fl.query(out_fields=query_fields, return_geometry=True, Dates_as_datetime = True)

**Describe alternatives you've considered**
current work around it to convert it to a datetime object, whihc seems unecessary.

**Additional context**
Add any other context or screenshots about the feature request here.

Start at the FeatureLayer query entry point shown as fl.query, then trace how date fields become timestamps. Define how the requested datetime option should preserve timezone information and avoid the reported microsecond change. Done means query results can return timezone-aware Python datetime objects while existing behavior remains available.

Scritto dal modello di indicizzazione a partire dal testo della issue.