Add schema ver to multitenant

[withdave]

When storing tenant-specific data files, we should include the current app schema version in the file path. This helps isolate schema changes across tenants and prevents a failure in one tenant (e.g. due to unrelated data issues) from breaking downstream telemetry apps that consume shared paths.

Justification:

• Prevents stale or partial data from a single tenant affecting the parent app.
• Aligns with the existing version tagging used within the tenant QVDs.
• Makes debugging and rollbacks easier by preserving version history.

Expected behaviour:

• The reload analyzer should insert the schema version (e.g. v1.3) into the file path for each stored QVD.
• Parent apps will load only data files matching their version.
• A TRACE should list when tenants have outdated files. Consider logging this into another file/ into the app for health tracing