[Requirements] Add support to reference use cases

[schnuerle]

With the new Policy program Requirements endpoint there is an opportunity to align agency data sharing requirements and operating programs with externally specified use cases.

Describe the solution you'd like

An array of use case ids could be added for each program, with a name , info link, and database link to the use case database that is being referenced. For example, the 'OMF Use Cases' could be referenced by this info link and this database link, and IDs like 'OMF-1', 'OMF-10' could be added to the database so each use case could be referenced.

Cities could create their own use case list, or refer to use cases created by providers, or by non-profits, or by any other data standards organizations.

Is this a breaking change

• I'm not sure

Impacted Spec

For which spec is this feature being requested?

• policy

Describe alternatives you've considered

N/A

Additional context

Referring to use cases can help agencies communicate their needs for MDS data more clearly, and can help where there is a legal or procedural need to articulate use cases, like GDPR in Europe. Amsterdam's draft standard CDS-M has a 'city-license' file that it much like Requirements, and there is a section with an array of use case IDs called useCasesCovered.

[schnuerle]

We now have an ID column on our use case database that can be referenced in the format 'OMF-MDS-##'.

[schnuerle]

Added this in PR #813 which you can browse in the PR and here: https://github.com/openmobilityfoundation/mobility-data-specification/tree/feature-requirements-3/policy#requirement-apis

Includes example linking to OMF's Use Case Database and CDS-M's use cases: https://github.com/openmobilityfoundation/mobility-data-specification/blob/feature-requirements-3/policy/examples/requirements.md#provider-and-other-apis

[schnuerle]

Resolved with #813