Use DDEV also for Evaluator guide

For the evaluator persona, who could be all kinds, such as project leaders, investors, somebody looking for a CMS system as a shop owner, for their developers to use, etc. I think we should aim at the lowest technical knowledge requirements for maximum inclusivity, to lessen the risk of driving away potential users, or decision makers.

With that angle, requiring DDEV and the accompanying Docker fiddling would be too much, in my opinion. Better to stick to just have PHP as requirement, and then use the Quick start command.

Having said that, after the "intro install PHP bit", we could consider adding a sentence, that the Docker-based DDEV option exists, for the technically savvy users?

PS. While we're discussing Drupal Quick Start Command, it has a tendency to freeze hang after a few minutes. It would be great to get that sorted out before too long. #3271178: Quick start command installation stops responding

I missed that it was already mentioned, but that looks great. At first I thought it should be right after the PHP install section, but the current placement works well.

I apologize: That page is not generated from the Official Docs project anymore. It is now a freely editable page.

One of the original goals of the evaluator guide was to make it easy to throw away when you're done. #2993155: Draft "Evaluator Guide" Outline & Guide. Versus the local development guide which currently recommends ddev where the expectation is you're spinning up a site with the intent of coming back again tomorrow and doing more.

And I think at that time anyway the agreement was that installing Docker + DDEV meant it was no longer easy to just throw everything away when you're done. That said, I also think there's an argument to be made for differentiating between an evaluator who just wants to see what Drupal looks like and poke around in the UI a little (https://simplytest.me ...) versus I guess an evaluator who wants to spend a day or two poking around at some contributed modules and custom code and is looking for something that's a little more permanent than single use. And for whom tooling like Docker, etc. is likely already at least somewhat familiar.

As someone going through the process of transitioning from (a modified) Acquia Dev Desktop to DDEV, I can say that it has not been straightforward at all. There is a learning curve, especially for Windows users who don't already have WSL2 installed (DDEV currently steers Windows users towards WSL2).

I added a reference to simplytest.me on the Evaluator guide. I have no idea why the simplytest.me page itself doesn't tell you what the admin Username and Password are, so I added those too.

I modified a sentence on the Evaluator Guide, that already referred to DDEV, to direct to the https://www.drupal.org/docs/getting-started/installing-drupal/install-dr... instead of DDEV official docs.

I'd like to think that this change resolves this issue. Further discussion on the page, and the relevance of DDEV, can happen in #3399873: Evaluate the whole idea of the Evaluator guide.

Setting to RTBC based on my previous comment.