Break up daily scheduled service index

[lauriemerrell]

Description

This PR:

• Refactors int_gtfs_schedule__long_calendar to be more useful by expanding to the actual day level & fixes a bug where Sundays were miscoded
• Creates int_gtfs_schedule__all_scheduled_service, which will support @owades on add check for proper lead time for schedule updates #2047
• Fixes bugs in int_gttfs_schedule__daily_scheduled_service_index: one bug had Sundays miscoded so no calendar based Sunday service was appearing, and the other affected cases where a feed used both calendar and calendar_dates but had some service_ids that were unique to calendar_dates

TODO:

• Talk to @owades
• If we want to do this, update the existing _index table accordingly
• Do we want to materialize as a table? 🤔
• Add YAML
• Test warehouse image per @atvaccaro removed updates to poetry lockfile because it was causing unrelated issues

Resolves # [issue]

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation
• agencies.yml

How has this been tested?

dbt run -s +int_gtfs_schedule__all_scheduled_service+
dbt test -s +int_gtfs_schedule__all_scheduled_service+

Screenshots (optional)

[owades]

Thanks @lauriemerrell. Is the idea that this would go into the making of int_gtfs_schedule__daily_scheduled_service_index?

[lauriemerrell]

@owades yes, the idea is that this creates a new int_gtfs_schedule__all_scheduled_service table (which is not filtered based on which feed is in effect on a given day) that your check and the existing index table can both consume. Your check can do the version over version comparison and the existing index table can just filter to only the feed versions we want to keep.

[owades]

Thank you! Looks good.