NEW: Add Packageworks setup to selfserve publishing

[stefanunity]

Description

We need to move package pack, verification and publishing to PackageWorks so we can publish ourselves moving forward.

• installed Wrench tooling
• customized jobs to fit our package
• generated yml files

Testing status & QA

• All the new jobs are green
• packed package has the same contents as if packed with our old job

Overall Product Risks

Very little risk, all the old jobs still exist and we can release with them until RM stops us.

• Complexity: low
• Halo Effect: none

Comments to reviewers

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.

[jfreire-unity]

Thanks for doing this!
If releasing works, maybe a intro about this to team would be great. Or just pointing in the right direction of internal documentation :)

[jfreire-unity]

Out of curioisity: when is this Python script called in the process?

[stefanunity]

it is called at the very beginning and you can then delete it

[jfreire-unity]

Do you know if this is true? Our releases have always been tagged commits in the stable branch. Unless we are changing this now or this is some other "branch pattern." I'm fine with either; I just want to surface this in case it becomes a problem.

[stefanunity]

I made a new branch called release/1.X and we need to follow this pattern says RM.
I'll update the release manual and it shouldn't be a big change for us.