WIP: Adds visual test addon page

[jonniebigodes]

With this pull request, the initial page for the visual testing addon is added to the documentation.

What was done:

• Created the page following the Chromatic 3.0 IA available here and currently available features at this stage that are not subject to additional design work or implementation.

[kylegach]

Suggested change

	Chromatic's Visual Testing addon helps you detect UI bugs during development. It enables you to run visual tests on your stories and compare changes with the latest baselines across multiple browsers and viewport sizes. Pinpoint visual changes in UI appearance and behavior and automate visual testing without leaving Storybook.
	Chromatic's Visual Testing addon helps you detect UI bugs during development. It enables you to run visual tests on your stories and compare changes with the latest baselines across multiple browsers and viewport sizes. Pinpoint changes in UI appearance and behavior and automate visual testing without leaving Storybook.

"visual" was redundant when describing "changes in UI appearance", and it also read funny with "visual testing" later in the sentence.

Otherwise, this intro is 🔥!

[elseloop]

I agree with Kyle here, this is a great intro!

[kylegach]

Suggested change

	Get started visual testing by introducing a change in one of your components; for example, change a background color or font size, save the file, and commit your local changes. Click the "Run tests" button in the toolbar to begin the process. This will:
	Get started visual testing by introducing a change in one of your components; for example, change a background color or font size. Then save the file, and commit your local changes. Click the "Run tests" button in the toolbar to begin the process. This will:

[kylegach]

@jonniebigodes — Sorry, I should've provided more specific guidance. I think it's best if we link to this comment on this issue, which details the workaround and why it may be necessary.

Suggested change

This is a [known issue](https://github.com/storybookjs/storybook/issues/22431) when using an older version of the Yarn package manager (e.g., version 1.x). To solve this issue, you can upgrade to the latest stable version. However, if you cannot upgrade, adjust your `package.json` file and provide a resolution field to enable the Yarn package manager to install the correct dependencies. In doing so, you may be required to delete your `node_modules` directory and `yarn.lock` file before installing the dependencies again.

This is a [known issue](https://github.com/storybookjs/storybook/issues/22431#issuecomment-1630086092) when using an older version of the Yarn package manager (e.g., version 1.x). To solve this issue, you can upgrade to the latest stable version. However, if you cannot upgrade, adjust your `package.json` file and provide a resolution field to enable the Yarn package manager to install the correct dependencies. In doing so, you may be required to delete your `node_modules` directory and `yarn.lock` file before installing the dependencies again.

[jonniebigodes]

@kylegach no need to be sorry whatsoever. I'm the one at fault. I had the link to Tom's comment saved, but copied over only issue 🤦

[kylegach]

This is solid work! Nicely done.

[elseloop]

These revisions look good to me! It's an excellent document.