CHANGE: Update ci to use new Package Verification Profile to generate errors

[stefanunity]

Description

We need to start moving to the new package works workflow for our releases. This is a first step adding the new PVP package checks to our pack job.

Changes made

• added new PVP execution to "Publish to Internal Registry (Dry Run)" yamato job
• added .\yamato\PVPexemptions.json file that includes all the errors the package currently generates
• any new errors will fail this job and you can see the report in the results tab of the job in yamato
• our grandfathered exemptsions being added to the system at https://github.cds.internal.unity3d.com/unity/pets.pvp-catalog/pull/23
• also fixed 2 small error categories as part of this PR (trainling spaces, wrong meta files)
• PVP-40-1 will complain about [Unreleased] in our changelog but won't be a problem on stable branch where that section will not exist during our package release

Testing

Job runs and the exemption file is beingused for checking errors.

Risk

Low risk, just adding another step, all previous steps of the job work the same.

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.

[ritamerkl]

Why do we remove this?

[stefanunity]

there were two Changed sections by mistake, I deleted one and this line also exists in the remaining section