feat: type Event.distance as float for non-integer distances

[fsalum]

Summary

The E1/F1 distance field (6 chars) can contain non-integer values — for example, "2.4" representing 2.4 miles in open-water meets. safe_cast(int, "2.4") raises ValueError and falls back to int() = 0, permanently losing the original value.

Per review, this PR types Event.distance as float (rather than adding a parallel distance_raw) and parses it with safe_cast(float, ...), so non-integer distances survive the parse.

Changes

• schemas.py: Event.distance is now float. get_or_create_event's distance param is typed float.
• e_event_parsers.py / f_relay_parsers.py: distance = safe_cast(float, extract(line, 16, 6)).

Compatibility

This is an API-compatible but data-changing release: integer distances now come through as floats (100 → 100.0), and callers that previously read distance as an int (e.g. keying events on it) should coerce. Blank/non-numeric fields still yield 0.0. Worth a major version bump.

Tests

• Float distance ("2.4" → distance=2.4)
• Integer distance ("1000" → distance=1000.0)
• Blank distance → distance=0.0
• Relay F1 float distance (same pattern)

All 116 tests pass.

[egelja]

Good catch! Can we instead update distance to a float? That's relatively backwards compatible, and more accurately represents the data

[fsalum]

Good catch! Can we instead update distance to a float? That's relatively backwards compatible, and more accurately represents the data

I'm only a bit hesitant to that because it would affect anybody using the library, they will start seeing some events with 2.4 FR swimming that is not pool but open water events. Worth perhaps bumping the version to 3.0 (backwards compatible but the data changed).

Let me know if you still want that and I'm fine updating it.

[egelja]

Yep, I'm fine with bumping. Let's do it!

[fsalum]

Updated.