Fix basic usage docs about environment activation

[Secrus]

Summary by Sourcery

Documentation:

• Updated the basic usage documentation to remove the outdated section about activating virtual environments and instead point to the relevant section in "Managing Environments".

[sourcery-ai]

Reviewer's Guide by Sourcery

This PR updates the documentation for activating virtual environments by removing outdated information and pointing to the dedicated "Managing Environments" section.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Removed the section on activating virtual environments using poetry shell or manual activation.	Removed instructions and explanations related to poetry shell, exit, deactivate, and manual virtual environment activation. Removed the table summarizing the different activation methods. Replaced the removed content with a reference to the "Activating the virtual environment" section in the "Managing Environments" documentation. Updated the note about not needing poetry shell when managing external virtual environments to remove the reference to poetry shell since it is no longer relevant given the other changes in this PR.	docs/basic-usage.md
Updated the note about using poetry run.	Removed the reference to poetry shell in the note explaining when to use poetry run. Clarified that poetry run is not needed when using an externally managed virtual environment that is already activated.	docs/basic-usage.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @Secrus - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider updating the note about external virtual environments to be consistent with the rest of the changes - it still implies different behavior for 'poetry run' vs 'poetry shell' while the latter command's documentation has been moved.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Deploy preview for website ready!

✅ Preview
https://website-i590pdj86-python-poetry.vercel.app

Built with commit c4d0512.
This pull request is being automatically deployed with vercel-action

[radoering]

Still in question: The linked section does not mention how to deactivate the environment. Should we keep this information somewhere?

[Secrus]

Still in question: The linked section does not mention how to deactivate the environment. Should we keep this information somewhere?

I am going to assume that someone who knows that they want to activate the environment, will know how to deactivate it. I would leave it as it is, we can add it later if we find that it is needed.