Update app setup instructions

[NoelDeMartin]

No description provided.

[netlify]

✅ Deploy Preview for moodledevdocs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	240fa6a
🔍 Latest deploy log	https://app.netlify.com/sites/moodledevdocs/deploys/6501a2ba667c65000801ffb6
😎 Deploy Preview	https://deploy-preview-733--moodledevdocs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 51	🟠 87	🟢 92	🟢 90	🟢 100	Report
/docs/apis/commonfiles	🔴 39	🟠 85	🟢 92	🟢 100	🟢 100	Report
/general/development/gettingstarted	🔴 45	🟠 87	🟢 92	🟢 90	🟢 100	Report
/general/releases	🔴 42	🟠 87	🟢 92	🟢 100	🟢 100	Report

[andrewnicols]

Hi Noel,

Whilst these changes are correct, I wonder if it may be worth suggesting the use of Chrome for Testing:
https://developer.chrome.com/blog/chrome-for-testing/

It's a separate version of Chromium for the purpose of testing and with automatic updates disabled.

[NoelDeMartin]

Thanks @andrewnicols for the suggestion, I wasn't familiar with "Chrome for Testing", I'll check it out.

However, for this PR, I think it's better if we go ahead with the merge because we're interested in getting it live before the DevJam. We thought this 119 version of Chrome wouldn't be a problem until November, but we just realized it's already being distributed for Chrome canary and Chromium so it can potentially affect some people :(.

We could update it to suggest using Chrome for Testing. But considering that it's the first time we hear about it in our team and none of us has used it, I'm prefer to keep suggesting Chromium which is what we all use. Eventually, when we test it ourselves, we can update the documentation.