Error handling for dbt retry (#3985)

## What are you changing in this pull request and why?
Added sample outputs to the `dbt retry` reference page

## Checklist

- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [x] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."

website/docs/reference/commands/retry.md

@@ -28,3 +28,80 @@ Retry works with the following commands:
 
 `dbt retry` reuses the [selectors](/reference/node-selection/yaml-selectors) from the previously executed command.
 
+
+Example results of executing `dbt retry` after a successful `dbt run`:
+
+```shell
+Running with dbt=1.6.1
+Registered adapter: duckdb=1.6.0
+Found 5 models, 3 seeds, 20 tests, 0 sources, 0 exposures, 0 metrics, 348 macros, 0 groups, 0 semantic models
+
+Nothing to do. Try checking your model configs and model specification args
+```
+
+Example of when `dbt run` encounters a syntax error in a model: 
+
+```shell
+Running with dbt=1.6.1
+Registered adapter: duckdb=1.6.0
+Found 5 models, 3 seeds, 20 tests, 0 sources, 0 exposures, 0 metrics, 348 macros, 0 groups, 0 semantic models
+
+Concurrency: 24 threads (target='dev')
+
+1 of 5 START sql view model main.stg_customers ................................. [RUN]
+2 of 5 START sql view model main.stg_orders .................................... [RUN]
+3 of 5 START sql view model main.stg_payments .................................. [RUN]
+1 of 5 OK created sql view model main.stg_customers ............................ [OK in 0.06s]
+2 of 5 OK created sql view model main.stg_orders ............................... [OK in 0.06s]
+3 of 5 OK created sql view model main.stg_payments ............................. [OK in 0.07s]
+4 of 5 START sql table model main.customers .................................... [RUN]
+5 of 5 START sql table model main.orders ....................................... [RUN]
+4 of 5 ERROR creating sql table model main.customers ........................... [ERROR in 0.03s]
+5 of 5 OK created sql table model main.orders .................................. [OK in 0.04s]
+
+Finished running 3 view models, 2 table models in 0 hours 0 minutes and 0.15 seconds (0.15s).
+
+Completed with 1 error and 0 warnings:
+
+Runtime Error in model customers (models/customers.sql)
+ Parser Error: syntax error at or near "selct"
+
+Done. PASS=4 WARN=0 ERROR=1 SKIP=0 TOTAL=5
+```
+
+
+Example of a subsequent failed `dbt retry` run without fixing the error(s):
+
+```shell
+Running with dbt=1.6.1
+Registered adapter: duckdb=1.6.0
+Found 5 models, 3 seeds, 20 tests, 0 sources, 0 exposures, 0 metrics, 348 macros, 0 groups, 0 semantic models
+
+Concurrency: 24 threads (target='dev')
+
+1 of 1 START sql table model main.customers .................................... [RUN]
+1 of 1 ERROR creating sql table model main.customers ........................... [ERROR in 0.03s]
+
+Done. PASS=4 WARN=0 ERROR=1 SKIP=0 TOTAL=5
+```
+
+Example of a successful `dbt retry` run after fixing error(s):
+
+```shell
+Running with dbt=1.6.1
+Registered adapter: duckdb=1.6.0
+Found 5 models, 3 seeds, 20 tests, 0 sources, 0 exposures, 0 metrics, 348 macros, 0 groups, 0 semantic models
+
+Concurrency: 24 threads (target='dev')
+
+1 of 1 START sql table model main.customers .................................... [RUN]
+1 of 1 OK created sql table model main.customers ............................... [OK in 0.05s]
+
+Finished running 1 table model in 0 hours 0 minutes and 0.09 seconds (0.09s).
+
+Completed successfully
+
+Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1
+```
+
+In each scenario `dbt retry` picks up from the error rather than running all of the upstream dependencies again.