Document the sync_job_statuses config option (#907)

Document the `sync_job_statuses` config option

Related to packit/packit-service#1943.
Merge after packit/packit-service#2470.

Reviewed-by: Laura Barcziová

Author: softwarefactory-project-zuul[bot]

docs/configuration/index.md

@@ -774,6 +774,13 @@ The information about releases [is retrieved from Bodhi](https://bodhi.fedorapro
 cache and required availability on Copr, it might take a while to get the
 newest state.
 
+#### sync_test_job_statuses_with_builds
+
+(*bool*) When set to `true` (the default), test job statuses are updated together with their corresponding
+build job statuses. When set to `false`, while test jobs are waiting for their corresponding build jobs
+to finish, their statuses remain in pending state and only build job statuses are updated, for example with
+`SRPM build is in progress...` or `Starting RPM build...`.
+
 ## User configuration file
 
 :::danger

docs/configuration/upstream/tests.md

@@ -226,6 +226,14 @@ The labels should be in the format of comma-separated string.
 You can also configure [`test_command.default_labels`](/docs/configuration#default_labels) to allow commonly used job combinations
 to be triggered without the need for manual specification.
 
+## Test job statuses
+By default, while test jobs are waiting for their corresponding build jobs to finish,
+their statuses share updates with the build jobs, for example `SRPM build is in progress...`
+or `Starting RPM build...`. This can be disabled by setting
+[`sync_test_job_statuses_with_builds`](/docs/configuration#sync_test_job_statuses_with_builds)
+to `false`. If disabled, test job statuses remain in pending state until their corresponding
+build jobs are finished.
+
 ## Creating Tests
 
 The easiest way to get started with defining tests is to use the [tmt][tmt] tool