[Workflows] Add VCS docs

[mia303]

Summary

Screenshots (optional)

Documentation checklist

• Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
• The change adheres to the documentation style guide.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/artifacts/	@elithrar, @dmmulroy, @mattzcarey, @dinasaur404, @whoiskatrin, @cloudflare/product-owners
/src/content/docs/workflows/	@elithrar, @rita3ko, @irvinebroque, @vy-ton, @celso, @deloreyj, @mia303, @jonesphillip, @cloudflare/product-owners

[github-actions]

Nimbus Preview URL: https://nimbus-cbd6cb65.preview.developers.cloudflare.com
Nimbus Preview Branch URL: https://nimbus-vcs.preview.developers.cloudflare.com

[dinasaur404]

this "/artifacts/deployments/get-started/" assumes a lot of knowledge from the customer

doesn't explain why they would use it, what it allows them to do

also base case is that i have my repo in artifacts, when i make a push to the repo, i want that to kick off a build. if it's on the main branch then it can kick off workflow to deploy to prod. if it's on non-main branch, then it can kick off workflow to create a preview.

[dinasaur404]

also most platforms are using APIs, not CLI. important to document how they'd use it that way.