Route /Skills paths to the Files API in databricks fs

[renaudhartert-db]

Changes

filerForPath now routes dbfs:/Skills/... to the Files API filer, alongside the existing /Volumes/ branch, instead of falling through to the legacy DBFS filer.

Why

UC Skills are Files-API-native: the server exposes skill bundle bytes at /api/2.0/fs/files/Skills/<catalog>/<schema>/<skill>/<file>, exactly like Volumes. This lets users manage a skill bundle with the standard databricks fs commands, e.g.:

databricks fs cp -r ./my-skill dbfs:/Skills/<catalog>/<schema>/my-skill/

fs cp -r walks the local tree and PUTs each file via the Files API (no atomic bundle endpoint — same as Volumes). The dbfs: scheme is legacy URI naming only; the request goes to the Files API.

Scope

One-line routing change. No new command, API method, or endpoint — reuses the existing public Files API, parallel to how /Volumes/ is handled. Shell completion already keys off the dbfs: scheme, so no completion change is needed.

Tests

Added new tests to cover Volumes and Skills.

This pull request and its description were written by Isaac.

[eng-dev-ecosystem-bot]

Integration test report

Commit: c99059d

Run: 30824183329

	Env	🔄​flaky	💚​RECOVERED	🙈​SKIP	✅​pass	🙈​skip	Time
💚​	aws linux		4	4	306	1070	8:51
💚​	aws windows		4	4	308	1068	5:27
🔄​	azure linux	4	4	4	301	1070	9:09
💚​	azure windows		4	4	307	1068	6:25
💚​	gcp linux		1	5	306	1070	6:56
💚​	gcp windows		1	5	308	1068	4:53

12 interesting tests: 4 RECOVERED, 4 SKIP, 4 flaky

	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
🔄​	TestFsCpFileToDirFileNotOverwritten	✅​p	✅​p	🔄​f	✅​p	✅​p	✅​p
🔄​	TestFsCpFileToDirFileNotOverwritten/uc-volumes_to_uc-volumes	✅​p	✅​p	🔄​f	✅​p	✅​p	✅​p
🔄​	TestFsRmEmptyDir	✅​p	✅​p	🔄​f	✅​p	✅​p	✅​p
🔄​	TestFsRmEmptyDir/uc-volumes	✅​p	✅​p	🔄​f	✅​p	✅​p	✅​p
💚​	TestFetchRepositoryInfoAPI_FromRepo	💚​R	💚​R	💚​R	💚​R	🙈​S	🙈​S
💚​	TestFetchRepositoryInfoAPI_FromRepo/root	💚​R	💚​R	💚​R	💚​R
💚​	TestFetchRepositoryInfoAPI_FromRepo/subdir	💚​R	💚​R	💚​R	💚​R

Top 5 slowest tests (at least 2 minutes):

duration	env	testname
2:59	aws windows	TestAccept
2:56	azure windows	TestAccept
2:56	gcp windows	TestAccept
2:47	azure linux	TestFilerWorkspaceFilesExtensionsReadDir
2:14	azure linux	TestFilerWorkspaceFilesExtensionsRead

[parthban-db]

Don't we have any file that records the api logs? That will basically capture which API we are using.