fix: improved documentation for how to use datasets in output schema (#2215)

We have changed how the output schema is rendered so I have updated the
documentation to make it clear and replaced the screenshot with a better
one.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Documentation-only changes that adjust examples and wording; no
runtime or API behavior changes.
> 
> **Overview**
> Updates the output-schema docs to reflect the new Console rendering of
dataset outputs: the dataset example now links to the full dataset
(`/items`) instead of separate per-view URLs, and clarifies that adding
a `view` query param only sets the default selected view.
> 
> Simplifies the combined dataset/collection example (removing multiple
dataset outputs/emojis), tweaks wording, and refreshes the referenced
Output-tab screenshot.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
37153f0. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Michał Olender <92638966+TC-MO@users.noreply.github.com>

Author: gippy

sources/platform/actors/development/actor_definition/output_schema/images/output-schema-combination-example.png

@@ -237,28 +237,8 @@ After you define `views` and `collections` in `dataset_schema.json` and `key_val
     "properties": {
         "overview": {
             "type": "string",
-            "title": "Overview 🔎",
-            "template": "{{links.apiDefaultDatasetUrl}}/items?view=overview"
-        },
-        "posts": {
-            "type": "string",
-            "title": "Posts ✉️",
-            "template": "{{links.apiDefaultDatasetUrl}}/items?view=posts"
-        },
-        "author": {
-            "type": "string",
-            "title": "Authors 🧑‍🎤",
-            "template": "{{links.apiDefaultDatasetUrl}}/items?view=author"
-        },
-        "music": {
-            "type": "string",
-            "title": "Music 🎶",
-            "template": "{{links.apiDefaultDatasetUrl}}/items?view=music"
-        },
-        "video": {
-            "type": "string",
-            "title": "Video 🎞️",
-            "template": "{{links.apiDefaultDatasetUrl}}/items?view=video"
+            "title": "Results",
+            "template": "{{links.apiDefaultDatasetUrl}}/items"
         },
         "subtitleFiles": {
             "type": "string",
@@ -274,7 +254,10 @@ After you define `views` and `collections` in `dataset_schema.json` and `key_val
 }
 ```
 
-The schema above defines five dataset outputs and two key-value store outputs. The dataset outputs link to views, and the key-value store output link to collections, both defined in their respective schema files.
+The schema above defines one dataset output and two key-value store outputs. The dataset output links to the entire dataset. In Apify Console, this displays as a table with a selector that lets users switch between views defined in the dataset schema. The key-value store outputs link to collections defined in
+the key-value store schema.
+
+If you add a `view` parameter to the dataset URL template, users still see the entire dataset in Apify Console, but the specified view is selected by default.
 
 When a user runs the Actor in the Console, the UI will look like this: