readme: mention vs code extension

[dberenbaum]

Adds a couple of brief references to the VS Code extension.

Questions/issues to consider:

• Where (else) in the readme should we mention the extension?
• Should we be giving any kind of summary or additional info about the extension in the DVC readme?
• The quickstart could be moved above "How DVC works", which would move up the reference to the extension. We should rewrite/reorganize the rest of the readme, but I didn't want to introduce unrelated changes in this PR.
• Studio might also be mentioned more and earlier (for example, when discussing sharing and comparing experiments), but this can be a separate discussion.

[shcheklein]

A few ideas:

• add badge (instead of donate - we don't need it and it's not very useful anyway)
• add link (section before badges)
• add a link in the line 26
• even more extreme add "in CLI (or VS code)" to the line 17
• mention in the installation section

[dberenbaum]

• add badge (instead of donate - we don't need it and it's not very useful anyway)

Removed donate mentions in a separate PR: #7862.

Did you have a particular badge in mind? For now, I added the version badge from https://github.com/cssho/VSMarketplaceBadge.

• add link (section before badges)

👍

• add a link in the line 26

Added for now. I worry the intro and "Why DVC?" become redundant. I would like to combine into a single bullet list in a separate PR.

• even more extreme add "in CLI (or VS code)" to the line 17

Take a look if this is what you meant. Again, I worry a little about being too redundant. I think we should decide between adding it here or adding it in the bullets.

• mention in the installation section

See what you think.

[shcheklein]

VS Code

[dberenbaum]

This doesn't accept whitespace. It's not visible anyway on the page, so I don't think it's an issue. Let me know if you think it's a problem.

[shcheklein]

It looks good to me, one small typo, otherwise I think it's good to go. I don't have any other major ideas and not sure anything else is needed.

I think we should decide between adding it here or adding it in the bullets.

I think it's fine to keep it redundant for now (for a few weeks) and we can cleanup it after.

[dberenbaum]

@shcheklein @jendefig Are there any important considerations for when this should be merged?

[shcheklein]

@dberenbaum let's merge it Monday end of the day? (there is a merge conflict, and could you please resolve the open conversations - just to make sure that you saw the feedback :) ).

[dberenbaum]

Well I forgot this is rst and not md 🤦 . Please hold.

[dberenbaum]

@shcheklein tldr changed to VS Code (I mistakenly thought rst couldn't handle whitespace there).