feat: improve documentation for scoped tokens

[tobice]

Changes:

• Add documentation for the new switch that controls access to default run storages (related issue)
• Add a Troubleshooting section that covers common pitfalls
• Improve tone in certain parts (less harsh)
• Standardize how permissions are referenced (always as Run, Write etc)

Some of the points are reflecting feedback from this thread.

[drobnikj]

It looks there are old screens, can you pls update them when you are doing changes there?

[TC-MO]

I proposed some changes to prose & headings phrasing to get around Vale as well as just clean it up a little bit.

Msoft style guide states that punctuation should not be used within headings as well as to use first person as little as possible to tried to address those too.

I also proposed changes to how permissions are shown, since they are part of UI within console I advise to just bold them and reserve backticks for code notation.

Let me know if those changes make sense to you, or if you have any questions.

[tobice]

@drobnikj Update the screenshot 👍

@TC-MO Thanks for the suggestions! As discussed offline, keeping most of them as they are. Given the Slack discussion and how easily people get confused, I wanted to make it eye grabbing 😊

[tobice]

Also, I will only merge it on Monday after the next apify-core release.