e.g. if we want to generate an ad-hoc 'profile' with which to validate data (in CoVE) or with which to determine which quality checks to run (in Data Quality Tool, e.g. finding all Period objects in the schema and then running period-specific checks).
Ensure that local file paths can be provided as a list to extension_versions parameter
If this is done, then, e.g. Kingfisher can have a post-scrape step to download all unique extensions referenced by packages. The ProfileBuilder can then use these to generate an ad-hoc 'profile' (#27), which can be made available to other steps (e.g. the check step).
The ocds-extensions-translations repo can still have po files for all versions, but we don't need to add old versions to Transifex, since almost no users (per Google Analytics) access them.