Add workflow and sidebar overview

[planteater]

• Adds performance-monitoring article to the "How to use CodeStream" section that goes into depth on the errors integration, and complements the other workflow articles.
• Adds a codestream-sidebar article as first article in the "CodeStream UI overview" section.
• Moves my-organization article to the "CodeStream UI overview" section.
• A little cleanup and tweaking to the codestream-new-relic article in the "Start here" section.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Hi @planteater 👋
Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

[gatsby-cloud]

Gatsby Cloud Build Report

docs-website-develop

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 25m

[paperclypse]

I've finished reviewing your PR @planteater. I made quite a few changes to bring this content a little more inline with our docs style guide. Let me know if you'd like to review them before I merge this in. Thanks!

[planteater]

@paperclypse - Yeah, we should discuss. If you look over the preview for the performance monitoring article it's become virtually unreadable. I'm not sure what the NR standards are regarding the use of image captions, but this clearly doesn't work.

https://docswebsitedevelop-planteaterdocswebsitefeaturewo.gtsb.io/docs/codestream/how-use-codestream/performance-monitoring/

Also the names of the first two sections in that article don't really make sense. The first section isn't about connecting NR to CS. It's showing that one way to open errors in CS is through the errors inbox. The second section isn't about CodeStream Observability, which one would read as observability about CodeStream. It's about being able to discover errors via CodeStream.

We also need to talk about the "New Relic CodeStream" thing. The application of that seems pretty arbitrary right now. Using it every time we say CodeStream certainly doesn't make sense. Having the overall section in the left rail say that seems reasonable, as well as the "What is New Relic CodeStream?" section, but after that it seems a bit excessive.