docs: preparing readme for public release

[arjunattam]

Preview readme is here: https://github.com/arjun27/playwright/blob/readme-2/README.md

This needs some more work—opening this to get suggestions. Things on my mind:

• The Puppeteer comparison question in FAQs needs more work. Currently, it feels focused on the implementation and not on the value to users. To communicate that better, I'm wondering if we should have a basic list of features. This list of features could then be used for comparisons against other tools (Cypress/Selenium) or among browsers. I have a draft list of features below, but I would need your help for comprehensiveness.
• Should we call out TypeScript as a differentiator with Puppeteer?
• CI badges: they don't work right now, I'm expecting them to show the correct status when the GH workflows become public with the repo.
• CI badges: our builds are failing, and it seems the issue is some rate limiting? Is there a way we could fix the build to pass before release?

Feature list

• Accessibility
• Emulation
• Input (mouse, keyboard)
• Generating PDFs, screenshots
• Geolocation
• Code coverage and performance metrics

[pavelfeldman]

I would remove the mention of the studio since it is not yet public. Otherwise, looks good.

[chirag04]

This list of features could then be used for comparisons against other tools (Cypress/Selenium) or among browsers. I have a draft list of features below, but I would need your help for comprehensiveness.

@arjun27 comparison with cypress and other tools will greatly help with decision making for folks wanting to introduce this in their stack. (Not to say that's how one should make a decision to use such a tool or not)