docs: Add guide for using CLI to populate code samples without GitHub Actions

[devin-ai-integration]

Add guide for using CLI to populate code samples without GitHub Actions

This PR adds a guide explaining how to use the Speakeasy CLI to generate and publish code samples for API documentation when not using GitHub Actions. The guide covers:

• Configuring the workflow
• Generating SDKs and code samples
• Promoting code samples to main using the tag promote command
• Accessing the public URL
• Integrating with Scalar
• Automating the process with custom CI pipelines

The guide follows Speakeasy documentation style guidelines and is based on information from a Slack thread discussing this workflow.

Link to Devin run: https://app.devin.ai/sessions/15110ade33394f2d8e5ab242e6c52bfc
Requested by: sagar@speakeasyapi.dev

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[github-actions]

🔗 Preview your changes
https://speakeasycom-git-docs-preview-pr-31-speakeasyapi.vercel.app
(The preview may still be building. Check back at this link in a few minutes.)

[chailandau]

@simplesagar is this good to go?

[devin-ai-integration]

I've updated the guide to clarify why promoting to the main tag is important by drawing a parallel to GitHub's main branch. The main tag in Speakeasy now has a clearer explanation that it represents production-ready code samples, similar to how the main branch in GitHub represents production-ready code.

[devin-ai-integration]

I've updated the guide to include the specific instruction about clicking "Integrate with Docs Provider" to find the URL to the OpenAPI with code samples combined. This clarifies exactly where users need to click in the Speakeasy dashboard to access the public URL.

[devin-ai-integration]

I've updated the guide to include a new section explaining why users would choose CLI tagging instead of GitHub Actions. The section highlights several advantages including platform independence, custom workflow integration, local development capabilities, support for private repositories, and compatibility with enterprise environments that have specific security requirements.

[devin-ai-integration]

I've removed the entire 'Important notes' section as suggested, since the information was already covered elsewhere in the guide. This makes the document more concise and focused.

[devin-ai-integration]

I've removed the line referring to integration guides documentation as suggested, making the guide more concise.

[devin-ai-integration]

I've updated the links to documentation providers with the correct paths as suggested, using the full paths to the integration guides in the /docs/integrations/ directory.

[devin-ai-integration]

I've confirmed that the Scalar integration steps have been removed as suggested. I've also cleaned up the extra blank line between sections to maintain consistent formatting.

[devin-ai-integration]

I've confirmed that the trailing slashes have been removed from the Scalar and ReadMe documentation provider links as suggested. The links now correctly point to the integration guides without trailing slashes.