Also publish to gh npm packages

[mattdean-digicatapult]

Pull Request

Checklist

• Have you read Digital Catapult's Code of Conduct?
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.

PR Type

Please delete options that are irrelevant.

• Bug Fix
• Chore
• Feature
• Documentation Update
• Code style update (formatting, local variables)
• Breaking Change (fix or feature that would cause existing functionality to change)

Linked tickets

Related to https://digicatapult.atlassian.net/browse/SQNC-50

High level description

Publish to gh npm packages as well as npm

Detailed description

Because https://github.com/digicatapult/sqnc-process-management published packages to both npm and github packages I've had to implement digicatapult/shared-workflows#18 so that we can publish to github. As this was a breaking change I'm updating here as well as part of that fix. As an aside this enables us to publish this package to github as well.

Describe alternatives you've considered

Could have just updated the permissions as the minimum. This doesn't really cost anything though and provides another registry option.

Operational impact

See digicatapult/shared-workflows#18 for rollback steps

Additional context

digicatapult/shared-workflows#18