## Summary

This PR make sure we consistently set the Elasticsearch project type.
There's a priority order for selecting the value:
1. If the Elasticsearch parameter `serverless.project_type` is already
provided (like e.g. in [this test
config](https://github.com/elastic/kibana/blob/main/x-pack/platform/test/serverless/functional/config.logs_essentials.base.ts#L21)),
we go with that value
2. if that's not the case, we check the options for a provided
`esProjectType` (typically comes from the CLI via `yarn es serverless
--projectType=X`)
3. If no Elasticsearch specific project type is provided, we fall back
to determining it from the Kibana project type, where for most projects
there's a 1:1 mapping - for the Kibana `es` project type we're
defaulting to `elasticsearch_general_purpose` which should be in line
with the behavior before this PR.

This change now requires to set the Elasticsearch project type correctly
on the CLI, e.g.
```
yarn es serverless --projectType elasticsearch_general_purpose
```
the `es` Kibana project type is no longer accepted.

### Other details
- The `yarn es serverless` CLI still accepts the `projectType` parameter
for the new `esProjectType` setting, so we're backwards compatible with
any current usage
- Value and type definitions for the project types and project tiers
have been streamlined to avoid duplicated listing of entries
- The Kibana `workplaceai` project type is now associated with the
`workplaceai` Elasticsearch project type
- We decided to keep the Scout runs as is for now (going with Kibana
project types)

## Summary

This PR make sure we consistently set the Elasticsearch project type.
There's a priority order for selecting the value:
1. If the Elasticsearch parameter `serverless.project_type` is already
provided (like e.g. in [this test
config](https://github.com/elastic/kibana/blob/main/x-pack/platform/test/serverless/functional/config.logs_essentials.base.ts#L21)),
we go with that value
2. if that's not the case, we check the options for a provided
`esProjectType` (typically comes from the CLI via `yarn es serverless
--projectType=X`)
3. If no Elasticsearch specific project type is provided, we fall back
to determining it from the Kibana project type, where for most projects
there's a 1:1 mapping - for the Kibana `es` project type we're
defaulting to `elasticsearch_general_purpose` which should be in line
with the behavior before this PR.

This change now requires to set the Elasticsearch project type correctly
on the CLI, e.g.
```
yarn es serverless --projectType elasticsearch_general_purpose
```
the `es` Kibana project type is no longer accepted.

### Other details
- The `yarn es serverless` CLI still accepts the `projectType` parameter
for the new `esProjectType` setting, so we're backwards compatible with
any current usage
- Value and type definitions for the project types and project tiers
have been streamlined to avoid duplicated listing of entries
- The Kibana `workplaceai` project type is now associated with the
`workplaceai` Elasticsearch project type
- We decided to keep the Scout runs as is for now (going with Kibana
project types)