docs: add release badge and LinkedIn badge

[terrytangyuan]

The categorization is to be consistent with Argo CD. Also added release badge and LinkedIn badge.

[terrytangyuan]

Is there a way to use the root level README file in the docs website? e.g. https://github.com/argoproj/argo-workflows/blob/main/docs/README.md is pretty redundant and we don't want to update both places every time.

[agilgur5]

I actually don't like the way Argo CD has badges with a lot of spacing and explicit categories, because that kind of defeats the purpose of badges as being small, aesthetically pleasing, in-line links.

If we wanted to do something similar, I would at least remove the double-spaced new-lines as suggested below, but I still think this is not quite how badges are intended to be used.

It also violates markdownlint & markdown conventions as well

[agilgur5]

this ignore is here because the first line is supposed to be an H1. If there's a line of badges first, I think that's ok, but putting several lines of text + badges would be an anti-pattern and would fail markdownlint multiple times. By convention, any text should be inside of / below headings

[agilgur5]

Is there a way to use the root level README file in the docs website? e.g. https://github.com/argoproj/argo-workflows/blob/main/docs/README.md is pretty redundant and we don't want to update both places every time.

If we want them to be equivalent, yes, I'm pretty sure there's a few ways to do it. They weren't the same until your #11358 I think, so that is a more recent change. I can handle that

[terrytangyuan]

Addressed comments

[terrytangyuan]

Agreed that this looks ugly. I re-purposed the PR to just add the additional badges.

[agilgur5]

If we want them to be equivalent, yes, I'm pretty sure there's a few ways to do it. They weren't the same until your #11358 I think, so that is a more recent change. I can handle that

I added a script for this in #12752. It's not quite a straight copy+paste because of needing to change relative and absolute links.