Add track imports and linked racing-line results

[rhorvath02]

What

Adds a Track analysis for importing paired boundaries from x1,y1,x2,y2 CSV files and generating a reusable centerline or minimum-curvature racing line. Vehicle width comes from Setup. Boundary previews and reports use closed cubic splines through every input point.

QSS Lap requires connected GGV and racing-line results. Both support drag connections in the tree. The lap inherits fidelity and power limits from its GGV and uses the saved line without optimizing it again. Changed track, width, clearance or source files invalidate the corresponding connection.

How to check

• Full local make ci: 1049 passed, 21 skipped before the final spline update.
• Final affected app, archive, track and lap tests: 163 passed. The nine track tests passed again after the final spline adjustment.
• Final lint and typecheck passed.
• Chrome: CSV upload, preview, saved configuration and racing-line drag connection passed without page errors.
• Michigan racing-line generation completed in 13.85 seconds. The linked 6 DOF QSS lap completed in 3.68 seconds including its report, with a 101.7045 second lap. The saved line samples were preserved exactly and line optimization ran zero iterations.

Notes

Stacked on #139. Vehicle clearance is constrained at paired gates, not continuously over the swept body between gates. The isolated OpenModelica baseline completed with 18 passed, one skipped and two failures. The four-post and ramp-steer mismatches match the prior audit run exactly. No baseline was changed.