Add publishing action

[zorkow]

This PR

• adds a publishing action
• renames the test action from test.js.yml to test.yml as the js bit does not make any sense!

I have tested the publishing action for the build. I need an npm authentication token for the final step.

[dpvc]

Should the .travis.yaml file be removed with this PR? I'm not sure how that is hooked in. I think there is a setting that should be removed for the repository as well.

I also was wondering about whether the tests need to be run here, but I guess if they are run on all the PRs, they don't have to be done here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.68%. Comparing base (c58d95f) to head (a890bdf).
Report is 5 commits behind head on develop.

Additional details and impacted files

@@            Coverage Diff             @@
##           develop    #1274     +/-   ##
==========================================
  Coverage    86.68%   86.68%             
==========================================
  Files          337      337             
  Lines        84105    84105             
  Branches      3125     4750   +1625     
==========================================
  Hits         72909    72909             
  Misses       11196    11196             

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[zorkow]

I've done the changes and it runs locally with act. Yet to be tested is the publish job.

[zorkow]

Should the .travis.yaml file be removed with this PR? I'm not sure how that is hooked in. I think there is a setting that should be removed for the repository as well.

I had forgotten to remove the .travis.yaml file, but that's gone now.

I also was wondering about whether the tests need to be run here, but I guess if they are run on all the PRs, they don't have to be done here.

Tests will run for every PR to develop branch, regardless whether or not test relevant files have changed. I have never worked out to restrict this to say "only changes in the ts directory". But I am also not sure if it is worth it, because you still want tests running when changing things like packages in package.json or changes in the components directory, etc.

[dpvc]

lgtm