docs: update all content to reflect new Workers API

Author: markjmiller

src/content/docs/workers/configuration/multipart-upload-metadata.mdx

@@ -5,6 +5,11 @@ title: Multipart upload metadata
 
 import { Type, MetaInfo } from "~/components";
 
+:::note
+
+There is a new API for uploading Workers. See [here](/workers/platform/infrastructure-as-code#cloudflare-rest-api) for more information.
+:::
+
 If you're using the [Workers Script Upload API](/api/resources/workers/subresources/scripts/methods/update/) or [Version Upload API](/api/resources/workers/subresources/scripts/subresources/versions/methods/create/) directly, `multipart/form-data` uploads require you to specify a `metadata` part. This metadata defines the Worker's configuration in JSON format, analogue to the [wrangler.toml file](/workers/wrangler/configuration/).
 
 ## Sample `metadata`

src/content/docs/workers/configuration/versions-and-deployments/index.mdx

@@ -69,6 +69,10 @@ When using [Wrangler](/workers/wrangler/), changes made to a Worker's triggers [
 New versions are not created when you make changes to [resources connected to your Worker](/workers/runtime-apis/bindings/). For example, if two Workers (Worker A and Worker B) are connected via a [service binding](/workers/runtime-apis/bindings/service-bindings/), changing the code of Worker B will not create a new version of Worker A. Changing the code of Worker B will only create a new version of Worker B. Changes to the service binding (such as, deleting the binding or updating the [environment](/workers/wrangler/environments/) it points to) on Worker A will also not create a new version of Worker B.
 :::
 
+#### Directly manage Versions and Deployments
+
+See examples of creating a Worker, Versions, and Deployments directly with the API, library SDKs, and Terraform in [Infrastructure as Code](/workers/platform/infrastructure-as-code/).
+
 ### View versions and deployments
 
 #### Via Wrangler

src/content/docs/workers/observability/logs/logpush.mdx

@@ -93,16 +93,6 @@ route = { pattern = "example.org/*", zone_name = "example.org" }
 
 </WranglerConfig>
 
-Configure via multipart script upload API:
-
-```bash
-curl --request PUT \
-"https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/scripts/{script_name}" \
---header "Authorization: Bearer <API_TOKEN>" \
---form 'metadata={"main_module": "my-worker.js", "logpush": true}' \
---form '"my-worker.js"=@./my-worker.js;type=application/javascript+module'
-```
-
 ## Limits
 
 The `logs` and `exceptions` fields have a combined limit of 16,384 characters before fields will start being truncated. Characters are counted in the order of all `exception.name`s, `exception.message`s, and then `log.message`s.