Add linting workflow to CI

[OliverStolzBO]

Run ESLint check when relevant files are changed.

[marbre]

How does this action work? Does it just run the linter (I am not familiar with typescript at all)? If yes, the linter will probably always pass if it isn't segfaulting. This means you need to check if there are changes to a prior / the checkin revision.

[OliverStolzBO]

The command eslint ./ (triggered by npm run lint) should check the code for linting errors according to the rules defined in the .eslintrc.js and return an error code if errors are found. Therefore the job should fail when linting errors exist.

[marbre]

The command eslint ./ (triggered by npm run lint) should check the code for linting errors according to the rules defined in the .eslintrc.js and return an error code if errors are found. Therefore the job should fail when linting errors exist.

As you say should, you don't seem to be 100% confident. What about introducing a formatting error in an additional commit to test the pipeline? This commit can be dropped before merging.

[OliverStolzBO]

The workflow acts as expected (See the workflow for the code containing a formatting error)