[ext-fintraffic] Persist and expose parking availabilityConditions

[teppope]

Note: Depends on PR #429 (lighting/cycle-storage) being merged first. This branch is based on feat/ext-fintraffic-parking-lighting.

Follow-up: Once entur/netex-parser-java#309 is merged and a new version is published, bump the netex-parser-java version in any consumer repo that needs the new AvailabilityCondition index (e.g. digitraffic-tis-parking-netex-migration). Tiamat does its own JAXB unmarshalling and is unaffected.

Summary

Persist and expose parking AvailabilityCondition elements (opening hours) in the Fintraffic ext layer.

What

• FintrafficParkingAvailabilityCondition (@Embeddable): stores dayTypeRef, isAvailable, startTime, endTime.
• FintrafficParking: new @ElementCollection field availabilityConditions backed by parking_availability_conditions table.
• V7 Flyway migration: creates parking_availability_conditions table + index on parking_id.
• Mapper import (FintrafficParkingMapperContributor): reads AvailabilityCondition elements from validityConditions, extracts day type ref, isAvailable, and first Timeband start/end; ignores non-AvailabilityCondition entries.
• Mapper export (FintrafficParkingMapperContributor): rebuilds AvailabilityCondition JAXBElements in the output Parking's validityConditions, appended after any existing ValidBetween entries.
• Merge importer (FintrafficMergingParkingImporter): copies availabilityConditions from existing record when merging so data is not lost.
• GraphQL (FintrafficParkingGraphQLTypeContributor): exposes availabilityConditions as a list of FintrafficAvailabilityConditionDto objects queryable via fintrafficParking { availabilityConditions { dayTypeRef isAvailable startTime endTime } }.
• Updater (FintrafficParkingUpdater): preserves existing conditions on updates.

Notes

• Ext-only change — no upstream Tiamat files are modified.
• AvailabilityConditions coexist with ValidBetween (soft-delete end date) in validityConditions.
• Tests: 58 ext tests pass (all Fintraffic* test classes).

Follow-up fix: NeTEx export failure for availability conditions

mapAvailabilityConditionsToNetex is invoked twice per export for the same target
Parking (a pre-existing Tiamat export-pipeline behavior). Two bugs surfaced as a result:

1. Wrong JAXB wrapping/type for Timeband/AvailabilityCondition elements — fixed to
   use the correct element type and wrapping expected by the XSD.
2. Duplicate ids from the double invocation — the method appended to the existing
   ValidityConditions_RelStructure list rather than replacing its own previously-added
   entries, so the second invocation duplicated entries with identical deterministic ids,
   violating the XSD's versioned-key uniqueness constraint. Fixed by removing any
   previously-added AvailabilityCondition entries before re-appending fresh ones
   (idempotent), while leaving unrelated entries (e.g. ValidBetween) untouched.

Verified with a real end-to-end regression test: GraphQL mutation sets
availabilityConditions, then the parent StopPlace is exported via the real
GET /api/services/stop_places/netex?idList= endpoint (the same one Kooste/PETI's
publication pipeline uses), confirming no 500 and correct XML content.

Follow-up fix (merged forward): Parking never appears in the Read API cache / NeTEx export failure for vehicle entrances

Brings in the fixes from #422 and #425:

• ReadApiNetexMarshallingService derived the Read API cache's type column from the
  runtime class name ("FintrafficParking") instead of the correct NeTEx element type
  name ("Parking"), making every new Parking permanently invisible to Read API queries.
• vehicleEntrances NeTEx export built elements without an id/version, violating the
  versioned-key XSD requirement.
• A test-only fix for a nested @TestConfiguration leaking into unrelated tests' contexts
  via the shared @ComponentScan, resolved by gating it with
  @Profile("fintraffic-read-api").