feat(edint-infraestructura): update to source ontology v0.2.1

[albertoabellagarcia]

Summary

Updates the edint-infraestructura candidate to the source ontology's current state (v0.2.0 -> v0.2.1), after being told the source repository had been updated.

1. Refresh of the 11 originally-translated models

• Namespace migration: the ontology's base IRI moved from vocab.linkeddata.es/.../infraestructura# to edint.es/def/infraestructura#. All context.jsonld IRIs updated to match, plus the InfrastructureType KOS concept namespace (.../kos/edint/InfrastructureType/ -> edint.es/kos/InfrastructureType/).
• Facility gained 3 properties: accessibility (string), isCadastralProperty (Relationship), locatedInZone (Relationship). All other 10 entities re-checked, no attribute-level changes.

2. Traffic/mobility branch brought into scope (8 new entities)

The original translation excluded this branch because it reused an ontology not included in the source repo. As of v0.2.1 it's natively defined (renamed to English, in the repo's own trafico#/zone#/catastro# sub-vocabularies), so the original exclusion no longer applies:

StreetSection, PlannedIncidence, UnplannedIncidence, TrafficEquipment, TrafficMeasuringDevice, TrafficObservation, RegulatedZone, CadastralProperty.

Bare Incidence and TrafficProperty are deliberately not materialized as their own entities -- same precedent as this candidate's existing Sensor/AccessSensor/CountingSensor and observableProperty handling (abstract bases and generic-Relationship targets aren't given their own entity). External vocabularies referenced by this branch (QUDT, W3C Time) aren't materialized either, consistent with how the rest of this candidate treats reused external building blocks.

Caveats (documented in full in standard-metadata.yaml)

• The source repo's own instance-data pipeline (examples/example.ttl) hasn't caught up with the namespace/notation changes in the formal ontology and SKOS files -- a real inconsistency in the upstream repo, not something introduced here. Facility's example keeps its real, verified infrastructureType value but flags this.
• owl:versionInfo reads 0.2.1, but the only tag at that version is v0.2.1-test ("no additions, test release" per its own GitHub release notes), and main has moved further since without a version bump. Translated against current main HEAD per explicit decision, not a stable tagged release.

Testing

• All 19 models (11 refreshed + 8 new) validated: every schema.json/context.jsonld/example file parses as JSON, every example.json validates against its own schema.json, $schemaVersion is 0.0.1 throughout.
• standard-metadata.yaml parses as YAML.
• Candidates index regenerated (tools/generate_index.py).