Improve private registry docs (#15216)

* Lead with basic git publish command

- Publish from git not a local path.
- Use the git protocol as, if you're using a sub-folder, it's not actually a valid web address.
- Mirror syntax as presented in the CLI docs.

* Expand versioning

- Add detail on including "v" in tags but not when publishing.
- Add full example workflow for publishing a version via git and Pulumi.
- Detail the default version lookup process.

* Remove local path examples

Use git source for all examples as local sources don't work.

* Remove protocol

* Refine versioning

- Move default behaviour to nearer the beginning.
- Make the wording more concise.

* Update content/docs/idp/get-started/private-registry.md

Co-authored-by: Florian Stadler <[email protected]>

---------

Co-authored-by: Florian Stadler <[email protected]>

Author: danielrbradley

content/docs/idp/get-started/private-registry.md

@@ -22,38 +22,46 @@ Developers leverage templates and components in their preferred workflows, wheth
 
 If you're new to Pulumi components, the [Build a Component](/docs/iac/using-pulumi/extending-pulumi/build-a-component/) guide is a great resource for getting started. Once you've authored your component, push it to a GitHub or GitLab repository that Pulumi can access. Private repositories are supported, but the repository must be open to inbound requests.
 
-#### Component Versioning
-
-Pulumi checks for a git version tag when the `publish` command is executed and stores it as the component version. The tag must adhere to [to the semantic versioning standard](https://semver.org/).
+The `publish` CLI command is used to publish components to the private registry.
 
-#### Component README
+```bash
+pulumi package publish <provider|schema>
+```
 
-A README is required when publishing a component. Pulumi renders markdown README files in the private registry. They're a great way to provide context for a component. By default, the Pulumi CLI looks for a README in the component's root directory. The `--readme` flag can be used to specify a custom source.
+For example, if your github organization is ACME and you are publishing the `k8s-cluster` component, you'd run:
 
 ```bash
-pulumi package publish /path/to/your/component --readme README_LOCATION
+pulumi package publish github.com/acme/k8s-cluster
 ```
 
-#### Specifying an Organization
+#### Component Versioning
 
-If you're part of multiple organizations and do not have a [default organization](/docs/iac/cli/commands/pulumi_org_set-default/) set, you must specify the org by using the `--publisher` flag.
+Pulumi uses git tags for versioning components. By default, the latest version tag will be used. The tag must adhere to [the semantic versioning standard](https://semver.org/) plus a "v" prefix (e.g. `v1.2.3`).
+
+To publish a specific version, append an `@` followed by the semver version (excluding the "v") after the git source.
+
+To create a version, push it to your "origin" git remote and publish to Pulumi's private registry, you'd run:
 
 ```bash
-pulumi package publish /path/to/your/component --publisher ORG_NAME
+git tag v1.2.3
+git push origin v1.2.3
+pulumi package publish github.com/acme/[email protected]
 ```
 
-#### CLI Publishing
+#### Component README
 
-The `publish` CLI command is used to publish components to the private registry.
+A README is required when publishing a component. Pulumi renders markdown README files in the private registry. They're a great way to provide context for a component. By default, the Pulumi CLI looks for a README in the component's root directory. The `--readme` flag can be used to specify a custom source.
 
 ```bash
-pulumi package publish COMPONENT_LOCATION
+pulumi package publish github.com/acme/k8s-cluster --readme README_LOCATION
 ```
 
-For example, if your github organization is ACME and you are publishing the `k8s-cluster` component, you'd run:
+#### Specifying an Organization
+
+If you're part of multiple organizations and do not have a [default organization](/docs/iac/cli/commands/pulumi_org_set-default/) set, you must specify the org by using the `--publisher` flag.
 
 ```bash
-pulumi package publish https://github.com/acme/k8s-cluster
+pulumi package publish github.com/acme/k8s-cluster --publisher ORG_NAME
 ```
 
 #### Authenticating with Private Repositories