Properly escape multi-segment path parameters

[mgyucht]

Changes

Ports databricks/databricks-sdk-go#869 to Python SDK. Subsumes #592.

Currently, path parameters are directly interpolated into the request URL without escaping. This means that characters like /, ? and # will not be percent-encoded and will affect the semantics of the URL, starting a new path segment, query parameters, or fragment, respectively. This means that it is impossible for users of the Files API to upload/download objects that contain ? or # in their name. / is allowed in the path of the Files API, so it does not need to be escaped.

The Files API is currently marked with x-databricks-multi-segment, indicating that it should be permitted to have / characters but other characters need to be percent-encoded. This PR implements this.

Tests

• Unit test for multi-segment path escaping behavior.
• Updated integration test to use # and ? symbols in the file name. This failed on main but succeeded on this PR.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 40.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 58.05%. Comparing base (7ae30e3) to head (1c02136).

Files	Patch %	Lines
databricks/sdk/service/files.py	14.28%	6 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #596   +/-   ##
=======================================
  Coverage   58.04%   58.05%           
=======================================
  Files          44       44           
  Lines       30071    30074    +3     
=======================================
+ Hits        17456    17459    +3     
  Misses      12615    12615           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.