docs: modify to detailed links + add details to running-locally

[da-head0]

Fixes #TODO

Motivation

When I first tried to install Argo Workflows using Dev Containers in my local environment, I was confused because the link to the The Visual Studio Code Remote - Containers and Dev-container CLI in the documentation didn't go to the link to extension or Dev-Container CLI itself, even though the context indicates that this is a link for that.

Also, as someone new to Dev Containers, I didn't know that I needed to use the make clean & make start to boilerplate, so I had to infer from the #Developing Locally section in the middle of the documentation how to get Argo Workflows running in my local environment.

The changes I've made to the documentation are located earlier in the documentation and would make getting up and running with Argo Workflows faster and easier for someone like me who is new to Argo Workflows or Dev Containers.

Modifications

• Modified the link of Dev Container extension in Visual Studio Code
• Modified the link of Dev Container CLI
• Added command for start the argo workflow inside Dev Container

Verification

[terrytangyuan]

@Joibel Could you help review this?

[da-head0]

@Joibel Could you help review this?

@terrytangyuan Thanks for your help. I was confused because all the spelling errors in the checks from the original running locally.md...

[agilgur5]

Dev-container CLI in the documentation didn't go to the link to extension or Dev-Container CLI itself

Good change! I think I stumbled upon this myself and just forgot about it as I don't use the CLI

so I had to infer from the #Developing Locally section in the middle of the documentation how to get Argo Workflows running in my local environment.

Hmm so it might make sense to just link downward to "Developing Locally" using its anchor #developing-locally. See below comment.
(I also see that the /etc/hosts part is no longer needed for the devcontainer since #11104 automated that)

I was confused because all the spelling errors in the checks from the original running locally.md...

Not sure why these just started showing up now 🤔 Seems to be erroring on code backticks. EDIT: see below comment, I figured that out
Wonder if there was a change in mdspell recently... EDIT: nope, it hasn't had a release in 6 years

[agilgur5]

Not sure why these just started showing up now 🤔 Seems to be erroring on code backticks.

there's 4 backticks on this line instead of 3 -- that's what's causing make docs-spellcheck to fail. it's just causing syntax errors in general.

you'll then also need to change "popup" to "pop-up" to fix the spelling.

[da-head0]

Thanks for letting me know!!

[da-head0]

I changed this draft pr to open. Please review when you have the time.

[agilgur5]

One small change requested, otherwise LGTM! 😃

[agilgur5]

LGTM. Thanks for working through the dev process and improving it!

[Joibel]

@Joibel Could you help review this?

LGTM thanks to @agilgur5's help