DO-2050: workflow for publishing node package

[crispy101]

Description of the proposed changes
Introduce workflow for publishing node package

Screenshots (if applicable)

Other solutions considered (if any)

Notes to PR author

⚠️ Please make sure the changes adhere to the guidelines mentioned in our contribution guide.

Notes to reviewers

ℹ️ When you've finished leaving feedback, please add a final comment to the PR tagging the author, letting them know that you have finished leaving feedback

Time Tracking

ABC-xxx: code review, select project XXXX

[tmthrgd-aligent]

Is this intended to replace our existing ad-hoc publishing workflows? Like https://github.com/aligent/cdk-constructs/blob/main/.github/workflows/changeset-release.yml, https://github.com/aligent/microservice-development-utilities/blob/main/.github/workflows/publish.yml, https://github.com/aligent/ts-code-standards/blob/main/.github/workflows/publish.yml and https://github.com/aligent/bigcommerce-api/blob/main/.github/workflows/publish.yml? Or are you intending us to only use this for new packages?

[crispy101]

Is this intended to replace our existing ad-hoc publishing workflows? Like https://github.com/aligent/cdk-constructs/blob/main/.github/workflows/changeset-release.yml, https://github.com/aligent/microservice-development-utilities/blob/main/.github/workflows/publish.yml, https://github.com/aligent/ts-code-standards/blob/main/.github/workflows/publish.yml and https://github.com/aligent/bigcommerce-api/blob/main/.github/workflows/publish.yml? Or are you intending us to only use this for new packages?

@tmthrgd-aligent This started mainly for FE repositories that don't have a publish workflow, and I didn't realise those ad-hoc ones. No need to rush to replace them now, IMO, but better to standardise the workflow at the end of the day.