add not_run to upstream docs + job statuses graph

Author: SashaLsnko

docs/guides/modules/orchestrate/pages/jobs-steps.adoc

@@ -85,6 +85,7 @@ stateDiagram-v2
     state "blocked or not running" as pending
     blocked --> pending : Job instructed to start but not yet started
     blocked --> unauthorized : Trying to use a context without permission
+    blocked --> not_run : Job's dependencies will never be satisfied
    
     pending --> running
     
@@ -102,6 +103,7 @@ stateDiagram-v2
     success --> [*]
     canceled --> [*]
     unauthorized --> [*]
+    not_run --> [*]
 ----
 
 .CircleCI server job status transitions

docs/guides/modules/orchestrate/pages/workflows.adoc

@@ -204,10 +204,11 @@ workflows:
               - success
               - failed
               - canceled
+              - not_run
 ----
 
 * The `test` job waits for the `build` job, and only runs if the `build` job is successful.
-* The `cleanup` job waits for the `test` job, and runs regardless of whether the `test` job succeeds, fails, or is canceled.
+* The `cleanup` job waits for the `test` job, and runs regardless of whether the `test` job succeeds, fails, is canceled or is not run.
 
 TIP: Refer to the xref:reference:ROOT:configuration-reference.adoc#requires[Requires] section of the configuration reference.
 

docs/reference/modules/ROOT/pages/configuration-reference.adoc

@@ -2794,7 +2794,7 @@ Possible types of `requires` items:
 * Map of job name to status (a required job that must attain the specified status for the job to start) +
 * Map of job name to a list of statuses (a required job that must attain one of the specified status for the job to start)
 
-The possible *status* values are: `success`, `failed` and `canceled`.
+The possible *status* values are: `success`, `failed`, `canceled` and `not_run`.
 |===
 --
 
@@ -2819,6 +2819,7 @@ workflows:
             - deploy:
               - failed
               - canceled
+              - not_run
 
 ----