Outline thoughts for rt_vs_sched route aggregation

[tiffanychu90]

• Jot down thoughts around issues to solve in rt_vs_schedule route-direction aggregation in route_aggregation.ipynb
• Add config.yml for rt_vs_schedule to show sub-folders within GCS
• Remove vp_spatial_accuracy script, now done with rt_v_scheduled_trip script
• Create long dfs with columns similar to what's outlined in Epic - GTFS Digest (exploratory portfolio) #989
• TODO: move shared_utils.utils_to_add to calitp_data_analysis --> fix parsing away of directory in utils.geoparquet_gcs_export

Main issues to address

1. Keep source data + metrics tightly defined with GCS bucket organization.
   vp_usable is source data for rt_vs_sched metrics, do not merge in schedule data until gtfs_digest report. Only bring in schedule_gtfs_dataset_key column in vp_usable + route_id-direction_id for trips also present in schedule. If not in schedule, fill it with route_id = Unknown and direction_id as Int64
2. Add function to concatenate trip file, enable us to put in 1 day or 7 days for aggregation
3. A single function for normalized metrics (percent, per min, etc)
4. A single function for aggregation (summing up numerator / denominator)

[github-actions]

nbviewer URLs for impacted notebooks:

• rt_scheduled_v_ran/scripts/route_aggregation.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• rt_scheduled_v_ran/scripts/route_aggregation.ipynb

[github-actions]

nbviewer URLs for impacted notebooks:

• rt_scheduled_v_ran/scripts/route_aggregation.ipynb