[Elasticsearch] Forward active.only config to datastream config

[crespocarlos]

What does this PR do?

This PR fixes a bug caused by the fact that the active.only flag was not being forwarded to the index_recovery data stream configuration.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test

• Pull this branch
• run elastic-package stack up
• cd packages/elasticsearch && elastic-package service up
• Toggle the "Fech active index only" flag

• When on, there shouldn't be any docs with stage: DONE in metrics-elasticsearch.stack_monitoring.index_recovery-* index
• When off there will be docs with stage: DONE

Related issues

closes #5466

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-10T17:42:04.535+0000

• Duration: 30 min 14 sec

Test stats 🧪

Test	Results
Failed	0
Passed	60
Skipped	0
Total	60

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (5/5)	💚
Files	100.0% (9/9)	💚
Classes	100.0% (9/9)	💚
Methods	87.5% (98/112)	👍 54.167
Lines	91.98% (562/611)	👎 -8.02
Conditionals	100.0% (0/0)	💚

[klacabane]

🚢

[elasticmachine]

Package elasticsearch - 1.7.3 containing this change is available at https://epr.elastic.co/search?package=elasticsearch