Use the proper umb-input-date events in the log viewer date range element

[lauraneto]

The log viewer date range input was changed from using input to umb-input-date, but the event handlers weren't updated accordingly.

If there's an existing issue for this PR then this fixes #19382.

[Copilot]

Pull Request Overview

This PR updates the log viewer date range selector to use the correct umb-input-date event handlers and refactors how date changes propagate to the workspace context.

• Switched from global input listeners and manual showPicker() hacks to per-field @change handlers.
• Imported UUIInputEvent and introduced dedicated #setStartDate/#setEndDate methods that call a shared #updateFiltered helper.
• Removed unused queryAll and cleaned up event listener setup/teardown.

Comments suppressed due to low confidence (2)

src/Umbraco.Web.UI.Client/src/packages/log-viewer/components/log-viewer-date-range-selector.element.ts:69

• After removing the manual showPicker() click handlers, verify that the date picker still opens on click by default; otherwise users may be unable to invoke the calendar UI.

<umb-input-date @change=${this.#setStartDate}

src/Umbraco.Web.UI.Client/src/packages/log-viewer/components/log-viewer-date-range-selector.element.ts:70

• Confirm that umb-input-date emits a change event when its value updates; if you need to capture every keystroke or immediate edits, consider using @input or the component-specific @value-change event instead of @change.

@change=${this.#setStartDate}

[AndyButland]

Looks good and tests out nicely. I can see the data filters being applied and they are retained now after amending the error level filter.