Update TTL values in spec examples

[richfab]

Context

During a workshop at the 2024 MobilityData Summit in Montreal, participants reported that the TTL (Time to Live) values in the spec examples did not show good practice. This PR aims to correct this.

TTL is used to improve the performance and manage the caching of data.

What's Changed

The TTL values in the spec examples were updated as follows:

Non-real-time files:

File	Before	After
gbfs.json	0 sec	300 sec
manifest.json	0 sec	300 sec
gbfs_versions.json	0 sec	300 sec
system_information.json	1800 sec	300 sec
vehicle_types.json	0 sec	300 sec
station_information.json	0 sec	300 sec
system_regions.json	86400 sec	300 sec
system_pricing_plans.json	0 sec	300 sec
geofencing_zones.json	60 sec	300 sec

Real-time files (no change):

File	Before	After
station_status.json	0 sec	0 sec
vehicle_status.json	0 sec	0 sec

Close to real-time file (no change):

File	Before	After
system_alerts.json	60 sec	60 sec

Acknowledgements

Thanks to the Montreal workshop participants and the community for contributing to the GBFS spec 🙏

Upcoming GBFS workshop dates:

• Paris, France: June 24-25, 2025
• Los Angeles, USA: October 7-8, 2025

[fredericsimard]

LGTM!