[1.8] remove dagster/storage_kind from docs (#23416)

Per [this
discussion](dagster-io/internal#10821),
we decided we weren't ready to commit this functionality, so walking
this back.

(cherry picked from commit 460f717)

docs/content/concepts/metadata-tags/tags.mdx

@@ -62,14 +62,6 @@ def leads(): ...
 
 Other APIs that define assets can also accept tag arguments, such as <PyObject object="AssetSpec" />, <PyObject object="AssetOut" />, <PyObject object="AssetOut" />, and <PyObject object="graph_asset" decorator />.
 
-#### Standard asset tags reference
-
-The following table holds standard asset tag keys defined by Dagster. The `dagster` prefix indicates that the Dagster package takes responsibility for defining the meaning of these tags.
-
-| Key                    | Description                                                       |
-| ---------------------- | ----------------------------------------------------------------- |
-| `dagster/storage_kind` | The technology used to store the asset, e.g. "snowflake" or "s3". |
-
 ### Jobs
 
 Adding tags to a job will attach them to every run executed by the job.
@@ -168,6 +160,24 @@ height={1406}
 
 ---
 
+## References
+
+### System run tags
+
+The following table lists the tags Dagster will, on occasion, automatically add to runs.
+
+| Tag                     | Description                         |
+| ----------------------- | ----------------------------------- |
+| `dagster/op_selection`  | The op selection for the run        |
+| `dagster/partition`     | The partition of the run            |
+| `dagster/schedule_name` | The schedule that triggered the run |
+| `dagster/sensor_name`   | The sensor that triggered the run   |
+| `dagster/backfill`      | The backfill ID                     |
+| `dagster/parent_run_id` | The parent run of a re-executed run |
+| `dagster/image`         | The Docker image tag                |
+
+---
+
 ## Related
 
 <ArticleList>