Update docs on installing development requirements

[ElenaKhaustova]

Description

Solves #2519

Docs update following the kedro-org/kedro-starters#238

Development notes

We updated docs in the development section related to linting and test requirements installation.

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[astrojuanlu]

I like how these docs look like! But wondering if we should also update the template

kedro/kedro/templates/project/{{ cookiecutter.repo_name }}/requirements.txt

Lines 5 to 8 in 6bf29f9

	pytest-cov~=3.0
	pytest-mock>=1.7.1, <2.0
	pytest~=7.2
	ruff~=0.1.8

otherwise our docs and the result of kedro new would be somewhat inconsistent

[ankatiyar]

💯

[ElenaKhaustova]

@ankatiyar, @astrojuanlu thank you for the review!

I've added some updates after your approval as e2e and unit tests were failing. In the tests we relied on the old format of requirements.txt for kedro project which included development requirements. We also use a separate starter template for e2e tests which I had to update: https://github.com/kedro-org/kedro/tree/main/features/steps/test_starter

Could you please take a brief look one more time?

Also, I found using a separate starter for e2e test a bit counterintuitive as I expected the default starter from the project to be used. What do you think of updating e2e test and copying the default starter instead of keeping separate one?

[ankatiyar]

Thanks for also fixing the tests @ElenaKhaustova!

[astrojuanlu]

LGTM!