docs: update setting up and running in cloud

[vdusek]

• I updated the "Setting up" and "Running in cloud" pages to make them more beginner-friendly (hopefully) and also removed mentions of Poetry. Including Poetry was unnecessary and could be confusing. Not to mention in Python there are X other package managers that we could hypotetically mention as well. So I decided to stay only with Pip and Pipx for templates. People using a package manager other than Pip will likely know how to handle the installation on their own.
• This was reported on Slack by @honzajavorek.

[honzajavorek]

🔴 I'd like to see the comment about apify init addressed, as that's my current roadblock when working on the Python course.

🔴 I don't know if you aim to support Windows, but if so, these documents need more love and verification that all works there as intended. AFAIK the venv creation and activation won't work for sure.

🟡 Otherwise I didn't find anything serious, just various unimportant nitpicks about lower/uppercase letters (I'm sorry!) and I offered several improvements to the flow of the text. I dig removing poetry from the mix.

[vdusek]

Thanks @honzajavorek for your review.

I'd like to see the comment about apify init addressed, as that's my current roadblock when working on the Python course.

I'm not sure how much detail we should provide about the Apify CLI and apify init specifically. Crawlee projects should be Actorizable like any other Python projects. If not, only the Crawlee-specific aspects should be mentioned here, while everything related to apify init should be covered in the Apify CLI docs. Mostly to ensure future-proof relevance. At least I've extended the section and added more reference to the CLI's docs.

I don't know if you aim to support Windows, but if so, these documents need more love and verification that all works there as intended. AFAIK the venv creation and activation won't work for sure.

@Pijukatel If it's not a problem, could you please address this? It is this comment.

[honzajavorek]

@vdusek That's a good point that while addressing the apify init part is important, it may be a task for a different tutorial than this one. Even in such case though, I think if you provide any kind of tutorial, the reader must be able to follow it seamlessly step-by-step, even if one of the steps is "setup your project according to this link", perhaps with "run this and if it works, you verified you can continue to another step" to make it more bulletproof. If you've done that, then I'm 👍 (I don't have time to re-read it right now, just replying to your comment.)