[Addition] Include script for "updating" 1.1 values to new format

[jbrown-xentity]

This information will help the Core Team resolve issues with the draft DCAT3-US application profile. So we can track all issues, please submit different issues in separate issue tickets. The Core Team will review and adjudicate the submitted issue and provide comments on this ticket indicating steps taken to address the issue as submitted.

Name: James Brown

Affiliation: GSA - data.gov

Type of issue: General Comment (Addition)

Issue:
Previous work: https://github.com/GSA/dcat-us3-tools/pull/1/changes#diff-2a5fa40069f196348a5302f566effdd7648888085dfe33c116fd4294b5e0400c

Include script for "updating" 1.1 values to new format (where applicable)

Previous work:
https://github.com/GSA/dcat-us3-tools/pull/1/changes#diff-2a5fa40069f196348a5302f566effdd7648888085dfe33c116fd4294b5e0400c

[neilmb]

CDOC Customer Experience Working Group and the tiger team were quite excited about the possibility of publishing a tool like this in Python alongside our schema.

[neilmb]

@SueValente Flagging this as a pottential data.gov task that we can do to help data providers.

[jbrown-xentity]

First pass was done here: https://github.com/GSA/dcat-us3-tools/blob/33dad947780125b5fe07bf66b47b826f67d60a1a/dcat-us3/fix_distribution_formats.py.
These changes may no longer be necessary for DCAT-US3.0 after tiger team edits, needs complete revamp.
Should test not just single agency source, but all sources.