Enhanced Diagnostics and Analytics

[GiribaldiTTV]

Overview

This PR addresses two related failure paths in TarkovMonitor:

• EFT/Steam log discovery failing or returning an unusable path.
• Watcher diagnostics causing the application UI to become difficult or impossible to use.

When EFT logs are unavailable, TarkovMonitor now remains open and usable. The watcher fails closed, reports the problem once, and can recover when a valid logs folder becomes available.

This addresses #187 and #210.

Watcher and log-path handling

GameWatcher now has a controlled watcher configuration and recovery flow.

The changes:

• Validate the EFT logs folder before enabling the watcher.
• Disable the watcher and process timer when the configured path is missing.
• Stop and clear stale log monitors when watcher configuration fails.
• Rebind the watcher when the folder still exists but FileSystemWatcher reports an error.
• Avoid running multiple watcher-recovery operations concurrently.
• Support resetting a custom log path back to automatic discovery.
• Cache failed automatic-path discovery so repeated property access does not continuously generate the same diagnostic.
• Preserve normal application operation when the watcher cannot start.

This is especially important for Steam installations, where the EFT installation and logs location may not be available through the same discovery path as a traditional installation.

Log monitor and readiness fixes

The previous monitor startup flow could miss initial-read events or count unsupported files while determining readiness.

The new flow:

• Recognizes only supported EFT log filenames.
• Supports both standard and _000 log filenames.
• Attaches monitor event handlers before starting the monitor.
• Safely replaces existing monitors when a newer log file is detected.
• Synchronizes monitor replacement and initial-read state.
• Handles empty, partial, and late-created log files without treating them as application-fatal conditions.
• Waits for the first readable application-log data before publishing application readiness.
• Prevents Tarkov.dev or tracker initialization from running against an unknown profile.

Settings and sidebar responsiveness

The Settings page previously performed default log-folder discovery from the CustomLogsFolder getter. Because that getter is used during rendering, a discovery failure could add a diagnostic while the UI was rendering.

That behavior has been changed so that:

• Log-folder discovery runs during component initialization or when the setting is reset.
• The discovered path is cached for rendering.
• The getter is now side-effect free.
• Repeated diagnostic messages are filtered before calling StateHasChanged().

This prevents a repeated watcher error from causing a diagnostic/render loop that makes Settings or the sidebar appear frozen, which is the user-facing behavior associated with #187.

Diagnostics improvements

• Diagnostic durations are optional instead of recording a misleading zero when timing was not measured.
• Operations that produce diagnostics now capture elapsed time where appropriate.
• Unmeasured durations are represented explicitly as [NOT_MEASURED].
• Local drive paths, UNC paths, temporary paths, and common Windows environment paths are redacted.
• Existing API-key, bearer-token, query-string, profile-ID, and sensitive-value redaction remains in place.
• Diagnostic handling is wired through watcher, UI, API, tracker, socket, media, persistence, and startup error paths.

Commit disposition

• 5fbe39d — Updates Tarkov.dev response-envelope handling so current API responses are processed correctly.
• 5fed92a — Adds the privacy-safe diagnostics model, redaction, diagnostic snapshots, and user-facing diagnostic flow.
• 5f9bf95 — Added development-only synthetic validation scaffolding. The final cleanup commit removes the test project and launcher from the repository so acceptance testing remains external and ignored.
• 12f1a9d — Improves Steam log discovery and keeps navigation available when watcher setup fails.
• a0c5e82 — Handles punctuated and future EFT session modes safely and fails closed for unsupported modes.
• b125d3d — Adds watcher recovery, late-log handling, synchronized initial-read tracking, Settings render protection, and explicit fixes for Handle PvpSeason session mode without flooding or freezing the Dashboard #187 and Steam installs can leave GameWatcher without a usable EFT logs path #210.
• c750f5b — Finalizes diagnostic timing and path redaction, removes committed development artifacts, and leaves the final PR scope focused on product changes.

Validation

• Product build passed with 0 errors.
• External injected-failure validation passed with failures=0.
• Missing-path handling, same-instance recovery, cached discovery failure, late log creation, application readiness, and synthetic watcher errors were validated.
• Steam discovery probe passed.

Fixes #187
Fixes #210

[Razzmatazzz]

Looks good, thanks!