Document table_update trigger in databricks_job resource (#5107)

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

Also improved validation for trigger-related attributes


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

- [x] `make test` run locally
- [x] 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

Author: alexott

NEXT_CHANGELOG.md

@@ -12,6 +12,7 @@
 
 ### Documentation
 
+* Document `table_update` trigger in `databricks_job` resource ([#5107](https://github.com/databricks/terraform-provider-databricks/pull/5107))
 * Document new attributes in `databricks_app` resource and data sources ([#5108](https://github.com/databricks/terraform-provider-databricks/pull/5108))
 * Document `git_email` in `databricks_git_credential` resource ([#5099](https://github.com/databricks/terraform-provider-databricks/pull/5099))
 

docs/resources/job.md

@@ -430,12 +430,17 @@ This block describes the queue settings of the job:
 
 * `pause_status` - (Optional) Indicate whether this trigger 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`.
 * `periodic` - (Optional) configuration block to define a trigger for Periodic Triggers consisting of the following attributes:
-  * `interval` - (Required) Specifies the interval at which the job should run. This value is required.
-  * `unit` - (Required) Options are {"DAYS", "HOURS", "WEEKS"}.
+  * `interval` - (Required, integer) Specifies the interval at which the job should run.
+  * `unit` - (Required, string) The unit of time for the interval.  Possible values are: `DAYS`, `HOURS`, `WEEKS`.
 * `file_arrival` - (Optional) configuration block to define a trigger for [File Arrival events](https://learn.microsoft.com/en-us/azure/databricks/workflows/jobs/file-arrival-triggers) consisting of following attributes:
   * `url` - (Required) URL to be monitored for file arrivals. The path must point to the root or a subpath of the external location. Please note that the URL must have a trailing slash character (`/`).
-  * `min_time_between_triggers_seconds` - (Optional) If set, the trigger starts a run only after the specified amount of time passed since the last time the trigger fired. The minimum allowed value is 60 seconds.
-  * `wait_after_last_change_seconds` - (Optional) If set, the trigger starts a run only after no file activity has occurred for the specified amount of time. This makes it possible to wait for a batch of incoming files to arrive before triggering a run. The minimum allowed value is 60 seconds.
+  * `min_time_between_triggers_seconds` - (Optional, integer) If set, the trigger starts a run only after the specified amount of time passed since the last time the trigger fired. The minimum allowed value is 60 seconds.
+  * `wait_after_last_change_seconds` - (Optional, integer) If set, the trigger starts a run only after no file activity has occurred for the specified amount of time. This makes it possible to wait for a batch of incoming files to arrive before triggering a run. The minimum allowed value is 60 seconds.
+* `table_update` - (Optional) configuration block to define a trigger for [Table Updates](https://docs.databricks.com/aws/en/jobs/trigger-table-update) consisting of following attributes:
+  * `table_names` - (Required) A non-empty list of tables to monitor for changes. The table name must be in the format `catalog_name.schema_name.table_name`.
+  * `condition` - (Required, string) The table(s) condition based on which to trigger a job run.  Possible values are `ANY_UPDATED`, `ALL_UPDATED`.
+  * `min_time_between_triggers_seconds` - (Optional, integer) If set, the trigger starts a run only after the specified amount of time passed since the last time the trigger fired. The minimum allowed value is 60 seconds.
+  * `wait_after_last_change_seconds` - (Optional, integer) If set, the trigger starts a run only after no file activity has occurred for the specified amount of time. This makes it possible to wait for a batch of incoming files to arrive before triggering a run. The minimum allowed value is 60 seconds.
 
 ### git_source Configuration Block
 

jobs/resource_job.go

@@ -594,6 +594,12 @@ func (JobSettingsResource) CustomizeSchema(s *common.CustomizableSchema) *common
 	s.SchemaPath("trigger", "table_update").SetExactlyOneOf(trigger_eoo)
 	s.SchemaPath("trigger", "periodic").SetExactlyOneOf(trigger_eoo)
 
+	s.SchemaPath("trigger", "periodic", "interval").SetValidateDiagFunc(validation.ToDiagFunc(validation.IntAtLeast(1)))                          // .SetRequired()
+	s.SchemaPath("trigger", "periodic", "unit").SetValidateFunc(validation.StringInSlice([]string{"DAYS", "HOURS", "WEEKS"}, false))              //.SetRequired()
+	s.SchemaPath("trigger", "file_arrival", "url").SetValidateFunc(validation.StringIsNotEmpty)                                                   // .SetRequired()
+	s.SchemaPath("trigger", "table_update", "table_names").SetMinItems(1)                                                                         //.SetRequired()
+	s.SchemaPath("trigger", "table_update", "condition").SetValidateFunc(validation.StringInSlice([]string{"ANY_UPDATED", "ALL_UPDATED"}, false)) // .SetRequired()
+
 	// Deprecated Job API 2.0 attributes
 	var topLevelDeprecatedAttr = []string{
 		"max_retries",