Migrate Code quality to Best Practices chapter

[vedran-kasalica]

Changes in this PR

The PR solves #377

Checklist

SIGNIFICANT changes / additions, e.g. new chapters

• I checked whether the contribution fits in The Turing Way before considering contributing to this Guide.
• I discussed my contribution in an issue and took into account feedback.

ALL contributions

• I previewed my changes locally using e.g. python3 -m http.server 4000 and confirmed they work correctly.
• I checked for broken links, e.g. using the link checker GitHub Action workflow, or locally by using docker run --init -it -v `pwd`:/docs lycheeverse/lychee /docs --config=docs/lychee.toml, at least for the files I changed.
• My name was added to the CITATION.cff file.

[c-martinez]

This looks good :-)

[c-martinez]

@egpbos , @fdiblen -- are there some EVERSE resources we could/should consider adding?

@jmaassen -- is it worth adding a link to EOSC quality TF?

[fdiblen]

Thank you @vedran-kasalica!

I suggested adding a link to RSQKit. The rest looks good for now.

[egpbos]

Alright, good to merge after rebasing on main.

[vedran-kasalica]

Alright, good to merge after rebasing on main.

I rebased it, so it can be merged as soon as it gets approved

[fdiblen]

looks good to me. Please resolve the conflicts before merging.

[egpbos]

Shit, sorry @vedran-kasalica can you please force push your branch again? :D

[vedran-kasalica]

Shit, sorry @vedran-kasalica can you please force push your branch again? :D

No worries @egpbos I just did, can you merge the PR, I am not authorized :)