Add core-http-compat in Search Documents

[JonathanCrd]

Packages impacted by this PR

@azure/search-documents

Issues associated with this PR

• [Search Documents] Add and implement core-http-compat #20939
• Move all packages that use core-http to use the newer Azure Core packages #15594

Describe the problem that is addressed by this PR

Search Documents has already migrated to the new Core client and Core rest pipeline libraries, however, this introduced too many breaking changes. In order to minimize the braking changes, core-http-compat was created. This PR regenerates the client with the latest version of autorest, with the core-http-compat-mode flag set to true, and no longer depending on core-http.

Checklists

• Added impacted package name to the issue description
• Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
• Added a changelog (if necessary)

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run js - [service] - ci

[JonathanCrd]

/azp run js - core - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[JonathanCrd]

/azp run js - search - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-sdk]

API changes have been detected in @azure/search-documents. You can review API changes here

API changes

- export interface SearchClientOptions extends CommonClientOptions {
+ export interface SearchClientOptions extends ExtendedCommonClientOptions {
- export interface SearchIndexClientOptions extends CommonClientOptions {
+ export interface SearchIndexClientOptions extends ExtendedCommonClientOptions {
- export interface SearchIndexerClientOptions extends CommonClientOptions {
+ export interface SearchIndexerClientOptions extends ExtendedCommonClientOptions {

[sarangan12]

LGTM