[412 and 408 HUBBLE ] - Automated linting

[laysabit]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the docs and the README with the added features, breaking changes, new instructions on how to use the repository.

Release planning

• I've decided if this PR requires a new major/minor/patch version accordingly to
  semver, and I've changed the name of the BRANCH to release/* , feature/* or patch/* .

What

This PR is part of the scope " Make github workflow checks more consistent between all data repos" and " Data repos should all run prettier or some kind of automated linting "

Why

To have a pattern in the data repositories for linting and tests.

Known limitations

[N/A]