[UR][L0] Fix incorrect profiling timestamps when events are reused (#21086)
Fix issue where urEventGetProfilingInfo returns stale timestamps when
profiling events are reused from cache. zeEventHostReset() does not
clear profiling data, causing zeEventQueryKernelTimestamp() to return
old timestamps.
This patch includes these changes:
- Prevents reusing events with profiling enabled from the cache,
ensuring each profiling measurement uses a fresh event.
- Fix reset() to clear timestamp fields.
- COMMAND_START case for timestamped events to return correct start
timestamp.
---------
Signed-off-by: Zhang, Winston <winston.zhang@intel.com>