[autoops_es] Add additional template to default excluded template patterns

**Describe the enhancement:**

The default excluded template patterns in [`x-pack/metricbeat/module/autoops_es/templates/templates.go`](https://github.com/elastic/beats/blob/main/x-pack/metricbeat/module/autoops_es/templates/templates.go#L24) skip Elastic-managed / system templates so that template metricsets (`cat_template`, `component_template`, `index_template`) only collect user-managed templates.

Two additional Kibana-managed system index patterns should be added to `defaultExcludedTemplatePatterns`:

- `.workflows-*`
- `.chat-*`
- `observability-*`
- rename `.lists-default*` to `.lists-*`

These cover Kibana-managed storage such as workflow definitions/events and chat/agent-builder indices (conversations, skills, tools, memory, and related backing indices). They belong in the same exclusion set as existing patterns like `.kibana*`, `.alerts*`, and `.fleet*`.

**Describe a specific use case for the enhancement or feature:**

Clusters running current Kibana versions create templates for `.workflows-*`, `observability-*` and `.chat-*`. Those templates are not user-managed and should not be collected. Adding the patterns to the default list keeps collection focused on application templates without requiring operators to set `IGNORE_TEMPLATES_BY_INDEX_PATTERN_NAME`.

Existing tests compare against `defaultExcludedTemplatePatterns`, so updating the slice should be sufficient.

Open x-pack/metricbeat/module/autoops_es/templates/templates.go and inspect defaultExcludedTemplatePatterns. Update the listed Kibana-managed patterns, including the .lists-* rename, then run the existing tests that compare against defaultExcludedTemplatePatterns. Done means those patterns are excluded while user-managed templates remain collectible.

Written by the indexing model from the issue text.