Support dots in target names when writing to an override block

[ilyakuz-db]

Stacked on #6138. Based on its branch so this diff shows only the target-name fix; rebase onto main once #6138 merges.

Problem

A target name may contain a dot — targets: {dev.eu: ...} passes bundle validate and deploys. But write-back addresses an override block by building targets.<target>.<field> as a string, which is then parsed back into path segments. A dotted name splits into two keys, so the write targets /targets/dev/eu/... and the command fails outright:

field not found in YAML configuration: op replace /targets/dev/eu/...: parent path /targets/dev does not exist

Pre-existing, not introduced by #6138: main fails the same way with a different message.

Solution

Build the prefix as path nodes instead of concatenating text. structpath.NewPatternStringKey already switches to bracket notation for a name that is not a plain field, so dev.eu renders as targets['dev.eu'] and round-trips as one key. Both the routed path and the unrouted fallback go through the same helper.

Tests

split/dotted_target edits a field in the override block of a target named dev.eu. It fails on both engines without this change (non-zero exit, nothing written) and passes with it. No other golden changes.

[github-actions]

Approval status: pending

/acceptance/bundle/ - needs approval

4 files changed
Suggested: @pietern
Also eligible: @denik, @andrewnester, @anton-107, @janniklasrose, @lennartkats-db, @shreyas-goenka

/bundle/ - needs approval

Files: bundle/configsync/blockindex.go, bundle/configsync/resolve.go
Suggested: @pietern
Also eligible: @denik, @andrewnester, @anton-107, @janniklasrose, @lennartkats-db, @shreyas-goenka

_{Any maintainer (@andrewnester, @anton-107, @denik, @pietern, @shreyas-goenka, @simonfaltum, @renaudhartert-db, @janniklasrose, @lennartkats-db) can approve all areas.
See OWNERS for ownership rules.}

[eng-dev-ecosystem-bot]

Integration test report

Commit: 1544e89

Run: 30845546883

	Env	💚​RECOVERED	🙈​SKIP	✅​pass	🙈​skip	Time
💚​	aws linux	4	4	334	1078	9:08
💚​	aws windows	4	4	324	1080	8:02
💚​	azure linux	4	4	334	1077	9:38
💚​	azure windows	4	4	324	1079	8:15
💚​	gcp linux	1	5	333	1079	10:55
💚​	gcp windows	1	5	323	1081	8:09

8 interesting tests: 4 RECOVERED, 4 SKIP

	Test Name	aws linux	aws windows	azure linux	azure windows	gcp linux	gcp windows
💚​	TestAccept	💚​R	💚​R	💚​R	💚​R	💚​R	💚​R
🙈​	TestAccept/bundle/invariant/no_drift	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S
🙈​	TestAccept/bundle/resources/vector_search_endpoints/drift/recreated_same_name	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S
🙈​	TestAccept/bundle/resources/vector_search_indexes/recreate/embedding_dimension	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S
🙈​	TestAccept/ssh/connection	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S	🙈​S
💚​	TestFetchRepositoryInfoAPI_FromRepo	💚​R	💚​R	💚​R	💚​R	🙈​S	🙈​S
💚​	TestFetchRepositoryInfoAPI_FromRepo/root	💚​R	💚​R	💚​R	💚​R
💚​	TestFetchRepositoryInfoAPI_FromRepo/subdir	💚​R	💚​R	💚​R	💚​R

Top 9 slowest tests (at least 2 minutes):

duration	env	testname
6:33	gcp windows	TestAccept
6:20	aws windows	TestAccept
6:10	azure windows	TestAccept
3:00	azure linux	TestAccept
2:54	gcp linux	TestAccept
2:48	aws linux	TestAccept
2:31	gcp windows	TestFilerReadWrite/workspace_files
2:22	azure linux	TestAccept/bundle/config-remote-sync/job_multiple_tasks/DATABRICKS_BUNDLE_ENGINE=terraform
2:04	azure linux	TestAccept/bundle/config-remote-sync/job_multiple_tasks/DATABRICKS_BUNDLE_ENGINE=direct