Full local paths emitted from QNN EP to telemetry

### Describe the issue

Full local paths are emitted through telemetry of ONNX Runtime QNN Execution Provider, like [here](https://github.com/microsoft/onnxruntime/blob/ab4831d83b7ed85f4c6192be38b9c59365e4e468/onnxruntime/core/providers/qnn/qnn_execution_provider.cc#L377), for example.
Full local paths may contain some private data, such as alias, if it's contained in the paths logged.
Paths logged and sent to telemetry should be anonymized in some way. An easy solution would be to remove full paths and keep only leaf file/dir names.

### To reproduce

1. Start trace logging.
2. Run an example which would target QNN EP, from a folder which contains user alias. For example, on Windows it would be C:\users\SomeUser.
3. Check if the trace log entry containing string "Using backend path:" has the user alias present. Look for other occurrences of user alias in the log as well.

### Urgency

_No response_

### Platform

Windows

### OS Version

26200.7462

### ONNX Runtime Installation

Built from Source

### ONNX Runtime Version or Commit ID

ab4831d

### ONNX Runtime API

C++

### Architecture

ARM64

### Execution Provider

Other / Unknown

### Execution Provider Library Version

_No response_

Start in onnxruntime/core/providers/qnn/qnn_execution_provider.cc around the linked telemetry path and reproduce the trace on Windows using a path containing a user alias. Inspect the entry containing "Using backend path:" and other logged occurrences for full local paths. Done means telemetry no longer exposes the local user path while retaining the needed path information.

Written by the indexing model from the issue text.