[Search] Generate SDK for 2026-05-01-preview (preview)

[efrainretana]

Task: Regenerate JavaScript SDK for API version 2026-05-01-preview for Azure Search (search-documents). Ensure to update customization files as needed to reflect the new API version. Ensure to run tests as well to validate the updated code. Tests should ALWAYS succeed unless they need to be re-recorded due to the new API version. If tests fail, investigate and fix the underlying issue — do not just update snapshots without understanding the failure.

Context

A new API version has been published to the TypeSpec spec repo and is ready for SDK generation.

Field	Value
API version	2026-05-01-preview
Release type	preview
Spec repo PR	Azure/azure-rest-api-specs#42217
Spec commit SHA	3d59fc2c21c51289ae7f0a6d4cb79aaff13d6b69
Internal ADO PR	N/A

The commit field in tsp-location.yaml must be set to the exact SHA above.
This SHA is the HEAD commit of the spec PR branch — it pins the generation to the exact spec state that was reviewed and approved.

---

Steps for Copilot

1. Update tsp-location.yaml
   File: sdk/search/search-documents/tsp-location.yaml
   Set the commit field to: 3d59fc2c21c51289ae7f0a6d4cb79aaff13d6b69
   Leave all other fields unchanged.

2. Run SDK generation from the repo root:

   npx tsp-client update --tsp-location sdk/search/search-documents/tsp-location.yaml

   If the azsdk CLI is available, you may also use:

   azsdk generate sdk/search/search-documents

3. Commit all generated changes
   Include both tsp-location.yaml and all generated source files.

4. Open a draft pull request targeting main with:

   • Title: [Search] Regenerate SDK for 2026-05-01-preview (preview)
   • Body: reference this issue and the spec PR (Azure/azure-rest-api-specs#42217)
   • Status: draft — do NOT mark it ready for review

---

Acceptance Criteria

• tsp-location.yaml commit field is exactly 3d59fc2c21c51289ae7f0a6d4cb79aaff13d6b69
• All generated source files reflect the new API version
• PR is in draft state
• PR body references this issue and the spec PR

---

Do NOT

• Do not manually edit any generated files beyond what tsp-client produces
• Do not mark the PR as ready for review
• Do not merge the PR