[Feature] Add a canonical `ts_original` lane for transport-stream sources

[CraigWatt]

Summary

VFO currently supports mkv_original, mp4_original, and m2ts_original lanes, but there is no first-class ts_original lane.

Why this matters

The codebase already recognizes .ts in some test/discovery paths, but there is no dedicated canonical lane for transport-stream sources. That makes TS handling inconsistent and less approachable than the other mezzanine/original workspace types.

Current state

Existing canonical source lanes appear to be:

• mkv_original
• mp4_original
• m2ts_original

There does not appear to be a corresponding ts_original workspace path or config marker.

Expected behavior

If VFO is intended to support transport-stream mezzanine inputs as a first-class lane, it should expose a canonical ts_original workspace and wire it through the same discovery/config/profile flow as the other original lane types.

Notes

This is separate from the existing bug work around mkv_original / mp4_original path handling. That bug should still be fixed independently.

Suggested follow-up

Decide whether ts_original should be:

• an alias for m2ts_original
• a distinct lane with its own runtime handling
• or intentionally unsupported, with the docs/tests updated to reflect that clearly