Remove unused EIS types (#5107)

They were removed in PR 4212.

(cherry picked from commit dcfb0ff)

# Conflicts:
#	output/schema/schema.json
#	specification/inference/_types/CommonTypes.ts

Author: pquentin

output/schema/schema.json

@@ -56,9 +56,8 @@
     "Dangling type 'indices._types:StringFielddata'",
     "Dangling type 'indices._types:StringFielddataFormat'",
     "Dangling type 'indices.stats:ShardFielddata'",
-    "Dangling type 'inference._types:EisServiceSettings'",
-    "Dangling type 'inference._types:EisServiceType'",
-    "Dangling type 'inference._types:EisTaskType'",
+    "Dangling type 'inference._types:DeepSeekServiceSettings'",
+    "Dangling type 'inference._types:DeepSeekServiceType'",
     "Dangling type 'ingest._types:PipelineFailure'",
     "Dangling type 'ml._types:CountFunction'",
     "Dangling type 'ml._types:DistinctCountFunction'",

output/schema/validation-errors.json

@@ -754,24 +754,32 @@ export class CohereTaskSettings {
   truncate?: CohereTruncateType
 }
 
-export class EisServiceSettings {
+export class DeepSeekServiceSettings {
   /**
-   * The name of the model to use for the inference task.
+   * A valid API key for your DeepSeek account.
+   * You can find or create your DeepSeek API keys on the DeepSeek API key page.
+   *
+   * IMPORTANT: You need to provide the API key only once, during the inference model creation.
+   * The get inference endpoint API does not retrieve your API key.
+   * After creating the inference model, you cannot change the associated API key.
+   * If you want to use a different API key, delete the inference model and recreate it with the same name and the updated API key.
+   * @ext_doc_id deepseek-api-keys
+   */
+  api_key: string
+  /**
+   * For a `completion` or `chat_completion` task, the name of the model to use for the inference task.
+   *
+   * For the available `completion` and `chat_completion` models, refer to the [DeepSeek Models & Pricing docs](https://api-docs.deepseek.com/quick_start/pricing).
    */
   model_id: string
   /**
-   * This setting helps to minimize the number of rate limit errors returned.
-   * By default, the `elastic` service sets the number of requests allowed per minute to `240` in case of `chat_completion`.
+   * The URL endpoint to use for the requests. Defaults to `https://api.deepseek.com/chat/completions`.
    */
-  rate_limit?: RateLimitSetting
-}
-
-export enum EisTaskType {
-  chat_completion
+  url?: string
 }
 
-export enum EisServiceType {
-  elastic
+export enum DeepSeekServiceType {
+  deepseek
 }
 
 export class ElasticsearchServiceSettings {