Cover what Dokploy v0.30 added

Six new resources, all backed by endpoints that did not exist before v0.30.0
and verified end-to-end against a live v0.30.2 instance:

  dokploy_network         Docker networks, now first-class. Services attach
                          through network_ids, which is what deprecates
                          Compose's isolated_deployment upstream.
  dokploy_dns_provider    Cloudflare or Route53, so adding a domain creates
                          its DNS record.
  dokploy_vault_provider  Env values resolved from HashiCorp Vault, Infisical,
                          AWS, Doppler, Azure or Scaleway at deploy time, so
                          the secret never lands in Dokploy or in state.
  dokploy_schedule        Cron jobs in a container, a stack, or on a server.
  dokploy_volume_backup   Scheduled backups of a named volume — the companion
                          to a mount that persists.
  dokploy_libsql          The sixth managed database engine.

libsql.create is the strictest endpoint in the API: eleven keys required to
be present, several only meaningfully null, no generated service name, and it
returns `true` rather than the row. CreateDefaults and ListIDs absorb all
three so the resource behaves like every other database.

Also filled the gaps a field-by-field diff against the live schema turned up:
domain gains `enabled` (the v0.30.0 park-a-domain toggle), compose gains
create_env_file, icon and service_networks, application gains icon and
preview_require_collaborator_permissions, and mounts accept libsql.

DNS and vault credentials are masked by Dokploy on read, so `config` is
tagged noread and keeps the configured value, as the basic-auth password
already does.

docs/resources/compose.md

@@ -40,6 +40,7 @@ Set `compose_file` to manage the stack definition inline (with `source_type = "r
 - `compose_file` (String) Inline Compose file contents. Used when `source_type` is `raw`.
 - `compose_path` (String) Path to the Compose file within the repository.
 - `compose_type` (String) Whether to run the stack with Docker Compose or Docker Swarm. Valid values: `docker-compose`, `stack`.
+- `create_env_file` (Boolean) Write the environment variables to a `.env` file next to the Compose file.
 - `custom_git_branch` (String) Branch to deploy for a custom Git remote.
 - `custom_git_ssh_key_id` (String) SSH key used to clone a private custom Git remote.
 - `custom_git_url` (String) Git remote URL, when `source_type` is `git`.
@@ -58,12 +59,14 @@ Set `compose_file` to manage the stack definition inline (with `source_type = "r
 - `gitlab_path_namespace` (String) Full GitLab namespace path.
 - `gitlab_project_id` (Number) Numeric GitLab project ID.
 - `gitlab_repository` (String) GitLab repository name.
+- `icon` (String) Icon shown next to the stack in the Dokploy UI.
 - `isolated_deployment` (Boolean) Run the stack on its own isolated Docker network.
 - `isolated_deployments_volume` (Boolean) Prefix volume names for isolated deployments. Retained for backwards compatibility.
 - `owner` (String) GitHub repository owner.
 - `randomize` (Boolean) Append a random suffix to service and volume names.
 - `repository` (String) GitHub repository name.
 - `server_id` (String) Remote server to deploy on. Omit to use the Dokploy host itself.
+- `service_networks` (String) Per-service Docker network attachments, as a JSON object mapping each service name in the stack to an array of network IDs.
 - `source_type` (String) Where the Compose file comes from. Valid values: `git`, `github`, `gitlab`, `bitbucket`, `gitea`, `raw`.
 - `suffix` (String) Suffix appended to generated resource names.
 - `trigger_type` (String) What triggers an automatic deployment. Valid values: `push`, `tag`.