Document task_retry_mode (#4993)

## Changes
<!-- Summary of your changes that are easy to understand -->

## Tests
<!--
How is this tested? Please see the checklist below and also describe any
other relevant tests
-->

- [x] `make test` run locally
- [ ] relevant change in `docs/` folder
- [ ] covered with integration tests in `internal/acceptance`
- [ ] using Go SDK
- [ ] using TF Plugin Framework
- [x] has entry in `NEXT_CHANGELOG.md` file

---------

Co-authored-by: Alex Ott <[email protected]>

Author: pranshupand-db

NEXT_CHANGELOG.md

@@ -11,6 +11,8 @@
 ### Bug Fixes
 
 ### Documentation
+* Document `continuous.task_retry_mode` in `databricks_job`  ([#4993](https://github.com/databricks/terraform-provider-databricks/pull/4993))
+
 
 ### Exporter
 

docs/resources/job.md

@@ -416,6 +416,10 @@ resource "databricks_job" "this" {
 
 * `pause_status` - (Optional) Indicate whether this continuous job is paused or not. Either `PAUSED` or `UNPAUSED`. When the `pause_status` field is omitted in the block, the server will default to using `UNPAUSED` as a value for `pause_status`.
 
+* `task_retry_mode` - (Optional) Controls task level retry behaviour. Allowed values are:
+  * `NEVER` (default): The failed task will not be retried.
+  * `ON_FAILURE`: Retry a failed task if at least one other task in the job is still running its first attempt. When this condition is no longer met or the retry limit is reached, the job run is cancelled and a new run is started.
+
 ### queue Configuration Block
 
 This block describes the queue settings of the job: