Bridge what Dokploy v0.30 added, and let the docs through

Six new resources from terraform-provider-dokploy v0.2.0 -- Network,
DnsProvider, VaultProvider, Schedule, VolumeBackup and Libsql -- plus the new
properties on Domain (`enabled`), Compose (`serviceNetworks`, `createEnvFile`,
`icon`) and Application. Verified with `pulumi up` against a live v0.30.2
instance: create, preview-clean, and destroy.

The upstream provider also now refuses a volume Mount with no `volumeName`,
which Dokploy would otherwise turn into an anonymous Docker volume recreated
on every deploy. That surfaces here at preview time, before anything exists.

Two things made that fix nearly invisible to Pulumi users, so this commit
fixes the second one: the bridge resolves the upstream `docs/` through the Go
module cache, where a locally `replace`d dependency never lands, so tfgen was
emitting every resource with no description at all. UpstreamRepoPath now
points at the checkout and all 445 inputs carry documentation -- with names
rendered per language, so Python readers see `volume_name` where TypeScript
readers see `volumeName`.

sdk/dotnet/Postgres.cs

@@ -10,6 +10,13 @@ using Pulumi;
 
 namespace Maxvojtkov.Dokploy
 {
+    /// <summary>
+    /// A managed PostgreSQL instance running on Dokploy.
+    /// 
+    /// &gt; Creating this resource provisions the service definition but does **not** start a deployment. Deploy it from the Dokploy UI or CLI.
+    /// 
+    /// &gt; Credentials are stored in Terraform state. Use a state backend with encryption at rest.
+    /// </summary>
     [DokployResourceType("dokploy:index/postgres:Postgres")]
     public partial class Postgres : global::Pulumi.CustomResource
     {