cemv_support - update schema

[skalexch]

Describe the problem

The vote to adopt cemv_support will start soon. If it is adopted, the schema needs to be updated. The field is an optional Enum so only unexpected_enum_value is to be added for both cemv_support fields in agency.txt and routes.txt.

Describe the new validation rule

Related spec language	Rationale for rule	Notice name to update or add	Pseudologic	Notice table columns	Severity	Notice description
agency.cemv_support	The value for cemv_support is either 0 or 1 or 2	unexpected_enum_value	If agency.cemv_support exists and is not in [0,1,2]:Trigger	csvRowNumber, fieldName, fieldValue, filename	ERROR	An enum has an unexpected value.
route.cemv_support	The value for cemv_support is either 0 or 1 or 2	unexpected_enum_value	If agency.cemv_support exists and is not in [0,1,2]:Trigger	csvRowNumber, fieldName, fieldValue, filename	ERROR	An enum has an unexpected value.

Sample GTFS datasets

No response

Severity

ERROR

Additional context

google/transit#545

[qcdyx]

Hey @skalexch is there a dataset available to test the new schema?

[skalexch]

@qcdyx TTC (mdb-732) has cemv_support. It's in agency.txt.