Provide CCM advanced property that queries due dates according to user time zone

The customer has users in different timezones across the globe. They are confused because work item queries that include Due Date filters return incorrect results. The current EWM design displays dates in work items according to the client timezone, but this is not adhered to when filtering on Due Date. If you filter to search for all Due Dates that fall on a certain day, work items in the server timezone that fall on that day are returned. Users with a different timezone will have skewed results to the extent that their timezone differs from the server timezone. For example, if the server is in London at UTC time, users in Sydney with UTC+10 will see results that include work items with Due Dates that fall up to 10 hours before the selected day. Work items with Due Dates on the day that fall in the last 10 hours from 2pm to 12 midnight will not be selected. So, depending on the location, some work items on the selected day are not selected, and some work items that fall prior or after the filtered day will be returned instead.

For this reason, we propose providing a CCM Advanced Property called "Query due dates according to user time zone" for users who wish to change the current behaviour. It changes the database query to instead filter according to the timezone of the client. Only a small calculation behind the scenes is needed to change this, which is to translate the time selected in the filter into the client timezone. They can name that query according to their timezone and use it and it would return correct results. If users are in different timezones, each user can create their own query.

The proposed design goes like this:

Example: The server is located in UTC time zone. The user is in Sydney (UTC+10 time zone).

1) The Due Date filter for the query is 2025-05-20 (that is, May 20, 2025). There are no other filters.

2) This date has no hours or minutes, so it is given 12 noon. That is, 2025-05-20 12:00:00.

3) Change that to Sydney time and it is: 2025-05-20 02:00:00 UTC (subtract 10 hours as Sydney is UTC+10). --> This calculation we propose to add. This doesn't happen in the present design.

4) Due Dates that are 12 hours on either side of that time are queried in the database. That is:

DUE_DATE >= 2025-05-19 14:00:00 (subtract 12 from 2:00)
DUE_DATE <= 2025-05-20 13:59:59 (add 12 to 2:00)

Note: The current design queries 10 hours after this:

DUE_DATE >= 2025-05-20T00:00:00Z
DUE_DATE <= 2025-05-20T23:59:59Z