Chore/#97 publish to npm

[kylejwatson]

Description

Changes package.json and workflow details in order to publish a public package to the NPM registry.

Changed the package scope as we only have access to the devoteam-nl scope/organisation on NPM. I also created the opendora NPM account as the owner and created a mailing list for current maintainers. Published here when manually running the workflow: https://www.npmjs.com/package/@devoteam-nl/open-dora-backstage-plugin

Issue

This PR addresses issue #97.

Contribution Checklist:

• [x] The pull request only addresses one issue or adds one feature.
• [x] The pull request does not introduce any breaking changes
• [x] I have added screenshots or gifs to help explain the change if applicable.
• [x] I have read the contribution guidelines.
• [x] I have ran the linting and formatting scripts to make sure the code is consistently styled.
• [x] I have built/compiled and ran the tests to make sure the code works correctly.
• [x] I have added or changed tests to cover new or different functionality, where applicable.
• [x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.

[goposky]

The open-dora-backstage-plugin github package visibility within was set to private, I just changed that to public. I presume it should work now publicly without needing authentication, and we could just host it here in github?

[kylejwatson]

https://www.npmjs.com/package/@devoteam-nl/open-dora-backstage-plugin - manually ran the workflow so it's not linked to a GitHub release yet. But publishing works correctly

[goposky]

Raised support request to reclaim npm org devoteamnl https://support.github.com/ticket/personal/0/2419203