Update the validate edge-case tests for the typed configuration

#7085 recorded main's behaviour. Where the typed configuration fixes a wrong
behaviour the Badness is gone (nested and shorthand timestamps, an inline
merge mapping, resources: null, a scalar targets section). Where it behaves
differently in a wrong way a Badness records it: scalar target variable
overrides inherited through a merge key, an aliased complex default rewritten
in place, duplicate and invalid merge keys, a duplicate default key, wrong
types turned into empty strings, the lost location of an unknown field in a
variable default, and presets that an include cannot clear.

Co-authored-by: Isaac <no-reply@databricks.com>

Author: denik

acceptance/bundle/validate/app_resource_duplicate_name_location/output.txt

@@ -2,7 +2,7 @@
 >>> [CLI] bundle validate
 Warning: invalid value "INVALID" for enum field. Valid values are [CAN_MANAGE CAN_MANAGE_RUN CAN_VIEW IS_OWNER]
   at resources.apps.app.resources[0].job.permission
-  in databricks.yml:13:25
+  in databricks.yml:17:25
 
 Name: test-bundle
 Target: default
@@ -15,7 +15,7 @@ Found 1 warning
 >>> [CLI] bundle validate -o json
 Warning: invalid value "INVALID" for enum field. Valid values are [CAN_MANAGE CAN_MANAGE_RUN CAN_VIEW IS_OWNER]
   at resources.apps.app.resources[0].job.permission
-  in databricks.yml:13:25
+  in databricks.yml:17:25
 
 [
   {

acceptance/bundle/validate/app_resource_duplicate_name_location/script

@@ -1,4 +1,4 @@
-# A diagnostic on a field of a duplicated app resource entry points at the first entry when the duplicate's value is the same.
+# A diagnostic on a field of a duplicated app resource entry points at the entry that is kept (the later one).
 errcode trace $CLI bundle validate
 
 # The entries are merged by name, the later one wins.

acceptance/bundle/validate/includes/clears_unforced_preset_values/test.toml

@@ -0,0 +1 @@
+Badness = "An include cannot clear a preset with \"\", 0 or false: the base value stays (a written zero is not recorded without ForceSendFields)."

acceptance/bundle/validate/includes/merge_failure_short_circuits_diagnostics/output.txt

@@ -1,9 +1,13 @@
 
 >>> [CLI] bundle validate
+Warning: unknown field: unexpected_after_failure
+  at bundle
+  in b.yml:2:3
+
 Error: cannot merge map with string
 
 Name: test-bundle
 
-Found 1 error
+Found 1 error and 1 warning
 
 Exit code: 1

acceptance/bundle/validate/includes/merge_failure_short_circuits_diagnostics/script

@@ -1,2 +1,2 @@
-# Includes after one that fails to merge do not report their diagnostics.
+# Includes after one that fails to merge still report their diagnostics.
 errcode trace $CLI bundle validate

acceptance/bundle/validate/includes/merge_failure_short_circuits_diagnostics/test.toml

@@ -1 +1 @@
-Badness = "The merge error has no location or path, and diagnostics of includes loaded after the failed merge (the unknown field in b.yml) are not reported, although they do not depend on the merge."
+Badness = "The merge error has no location or path."

acceptance/bundle/validate/nulls/resources_container/output.txt

@@ -1,9 +1,9 @@
 
 >>> [CLI] bundle validate
-Error: expected a map at "resources", found nil
-
 Name: test-bundle
+Target: default
+Workspace:
+  User: [USERNAME]
+  Path: /Workspace/Users/[USERNAME]/.bundle/test-bundle/default
 
-Found 1 error
-
-Exit code: 1
+Validation OK!

acceptance/bundle/validate/nulls/resources_container/script

@@ -1,2 +1,2 @@
-# resources: null is rejected.
+# resources: null is accepted.
 errcode trace $CLI bundle validate

acceptance/bundle/validate/nulls/resources_container/test.toml

@@ -5,5 +5,6 @@ Warning: expected string, found map
   in databricks.yml:15:23
 
 {
+  "bad.key[0]": "",
   "good": "ok"
 }