Make dependency management tasks more explicit

[christian-weiss]

On a fresh git clone + yarn install a new developer will get the following list of yarn warnings.

warning " > [email protected]" has unmet peer dependency "algoliasearch@>= 3.1 < 5".
warning " > [email protected]" has unmet peer dependency "react@>= 16.3.0 < 19".
warning " > [email protected]" has unmet peer dependency "react-dom@>= 16.3.0 < 19".
warning "react-instantsearch-dom > [email protected]" has unmet peer dependency "algoliasearch@>= 3.1 < 5".
warning "react-instantsearch-dom > [email protected]" has unmet peer dependency "algoliasearch@>= 3.1 < 5".
warning "react-instantsearch-dom > [email protected]" has unmet peer dependency "react@>= 16.3.0 < 19".
warning " > [email protected]" has unmet peer dependency "react@>=0.14.0".
warning " > [email protected]" has unmet peer dependency "react-dom@>=0.14.0".
warning " > @this-dot/[email protected]" has incorrect peer dependency "cypress@< 12.6.0".
warning " > [email protected]" has incorrect peer dependency "eslint@^4.0.0 || ^5.0.0".
warning " > [email protected]" has incorrect peer dependency "postcss@^8.4.14".
warning " > [email protected]" has incorrect peer dependency "webpack@^5.0.0".
warning " > [email protected]" has incorrect peer dependency "stylelint@^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0 || ^13.0.0".
warning " > [email protected]" has incorrect peer dependency "stylelint@10 - 13".

Currently it is not documented in this project what the current assessment of this team is:

• if it is safe to ignore this or
• if one should act and improve the project.

In addition to that new issues should bring the CI/CD pipeline to fail:

• to trigger an assessment,
• let team mates fix it or
• to document the reason why it is safe to ignore this warning/error