style(models): Replaces non-ASCII charactes in pdl files with ASCII c…

[nmbryant]

…haracters

Our team ran into some issues publishing the avro schema via Github actions due to non-ASCII characters in some of the pdl files. This PR replaces the non-ASCII characters with ASCII characters in the models.

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[jjoyce0510]

Going to approve, but can you explain exactly what the issue was? Why are non-ascii characters failing?

[nmbryant]

Thanks for merging this. With our setup, the GMS is not able to publish the schema if detects a difference in the schema when an object is updated so we publish the schema via Github Actions. When the project was built in Actions, the generated files had unknown characters for the characters in this PR and it published that. Because of that, the GMS would detect a difference and try to publish the schema and fail. We were able to get the workflow working properly by adding a flag to the build command, but figured that changing the characters to ASCII might prevent someone else from running into this.