### Elasticsearch Version

all serverless

### Installed Plugins

_No response_

### Java Version

_bundled_

### OS Version

all

### Problem Description

Creating a time series instance in Serverless fails with the following error:

```
elasticsearch.exceptions.RequestError: RequestError(400, 'illegal_argument_exception', 'Settings [index.time_series.end_time,index.time_series.start_time,index.routing_path] are not available when running in serverless mode')
```

### Steps to Reproduce

I used a custom Python client script to create an index

```
from elasticsearch import Elasticsearch
import sys
import argparse
import os

if os.environ.get('API_KEY') is None or os.environ.get('ELASTICSEARCH_URL') is None:
    print(f"Missing environment variables 'API_KEY' and 'ELASTICSEARCH_URL'")

api_key = os.environ.get("API_KEY")
elasticsearch_url = os.environ.get("ELASTICSEARCH_URL")

print(f"Using api key: {api_key}")
print(f"Using Elasticsearch url: {elasticsearch_url}")

client = Elasticsearch(
  elasticsearch_url,
  api_key=api_key
)

parser = argparse.ArgumentParser(description='Elasticsearch TSDB indexing')
parser.add_argument('dataset', help='The set of documents to index as a Json file')
parser.add_argument('index', help='The index where data will be indexed')

args = parser.parse_args()

mappings = {
    "settings": {
      "index": {
        "mapping.total_fields.limit": 10000,
        "codec": "default",
        "routing_path": [
          "cloud_region",
          "pod_id"
        ],
        "time_series": {
          "start_time": "2023-09-01T00:00:00",
          "end_time": "2023-09-30T23:59:59"
        }
      }
    },
    "mappings": {
        "properties": {
            "@timestamp": {
                "type": "date"
            },
            "cloud_region": {
                "type": "keyword",
                "time_series_dimension": "true"
            },
            "pod_id": {
                "type": "keyword",
                "time_series_dimension": "true"
            },
            "counter": {
                "type": "integer",
                "time_series_metric": "counter"
            },
            "gauge": {
                "type": "double",
                "time_series_metric": "gauge"
            }
        }
    }
}


delete_response = client.indices.delete(
    index=args.index,
    ignore_unavailable=True
)
print(f"Delete response: {delete_response}")

create_response = client.indices.create(
    args.index,
    body=mappings
)
print(f"Create response: {create_response}")
```

### Logs (if relevant)

_No response_
server/src/main/java/org/elasticsearch/index/IndexSettings.java
return switch (s) {
            case "false", "true", "checksum" -> s;
            default -> throw new IllegalArgumentException(
                "unknown value for [index.shard.check_on_startup] must be one of " + "[true, false, checksum] but was: " + s
            );
        };
    }, Property.IndexScope);
    /**
     * Index setting describing the maximum value of from + size on a query.
     * The Default maximum value of from + size on a query is 10,000. This was chosen as
     * a conservative default as it is sure to not cause trouble. Users can
     * certainly profile their cluster and decide to set it to 100,000
     * safely. 1,000,000 is probably way to high for any cluster to set
     * safely.
     */
    public static final Setting<Integer> MAX_RESULT_WINDOW_SETTING = Setting.intSetting(
        "index.max_result_window",
        10000,
        1,
        Property.Dynamic,
        Property.IndexScope
    );
    /**
     * Index setting describing the maximum value of from + size on an individual inner hit definition or
     * top hits aggregation. The default maximum of 100 is defensive for the reason that the number of inner hit responses
     * and number of top hits buckets returned is unbounded. Profile your cluster when increasing this setting.
     */
    public static final Setting<Integer> MAX_INNER_RESULT_WINDOW_SETTING = Setting.intSetting(
        "index.max_inner_result_window",
        100,