fix: add CI and MCP to MetaOrigin enum (#73)

Add the two `MetaOrigin` values the platform already emits but the
Python enum was missing, bringing it to parity with `apify-shared-js`:

- `MCP` — runs started through the Apify client triggered from the Apify
MCP server.
- `CI` — runs started from a CI/CD pipeline (e.g. GitHub Actions).

Without `MCP`, any Actor invoked via the Apify MCP server crashes at
startup: the released SDK line (`apify` 3.4.x) validates
`run.meta.origin` against `apify_shared.consts.MetaOrigin`, and an
unknown value raises a `pydantic.ValidationError` before user code runs.

Related: apify/apify-sdk-python#1032. The API OpenAPI spec is fixed in
parallel (apify/apify-docs#2752), which covers the SDK master line that
reads the enum from `apify-client` v3.

Author: vdusek

src/apify_shared/consts.py

@@ -350,6 +350,12 @@ class MetaOrigin(str, Enum):
     CLI = 'CLI'
     """Actor run started using the Apify command-line interface."""
 
+    CI = 'CI'
+    """Actor run started from a CI/CD pipeline (e.g. GitHub Actions)."""
+
+    MCP = 'MCP'
+    """Actor run started through the Apify client triggered from the Apify MCP server."""
+
 
 class StorageGeneralAccess(str, Enum):
     """Storage setting determining how others can access the storage.