Move away from env-id filters for tsdb charts (elastic#696)

This is effectively the same as elastic#689 for `tsdb*`.

The update queries (for `rally-races` and `rally-results`) were based on the example shown below, using `tsdb-time-series-synthetic-source-nightly`, `tsdb-standard-synthetic-source-nightly` and `tsdb-standard-nightly` as `user-tags.env-id` in combinarion with `tsdb-time-series-synthetic-source`, `tsdb-standard-synthetic-source`, `tsdb-standard` for `user-tags.benchmark-name` respectively.

```
POST rally-races-2022-*/_update_by_query
{
  "query": {
    "bool": {
      "must": [
        {
          "term": {
            "user-tags.env-id": "tsdb-time-series-synthetic-source-nightly"
          }
        },
        {
          "term": {
            "user-tags.setup": "esbench"
          }
        },
        {
          "term": {
            "environment": "nightly"
          }
        }
      ],
      "must_not": [
        {
          "exists": {
            "field": "user-tags.benchmark-name"
          }
        }
      ]
    }
  },
  "script": {
    "source": "ctx._source['user-tags']['benchmark-type'] = 'nightly'; ctx._source['user-tags']['benchmark-name'] = 'tsdb-time-series-synthetic-source'",
    "lang": "painless"
  }}
```