Adding Streams information into the Manage data section

[yetanothertw]

Refers to #274

• On the Data streams page added an admonition to mention Streams and link to it.

• Tutorial: Update the lifecycle of a data stream now has a new section Manage data retention in Streams.

• Tutorial: Configure data stream retention has been updated as well. This page may need to be reworked separately in the future as most of its content fits under conceptual type of information rather than tutorial.

• Failure store -- updated the Set up for existing data streams section to add a tip about performing that in Kibana.

• Modify a data stream -- updated but need to update links to Streams content after Mike's PR is merged.

• View the lifecycle status of an index or data stream -- updated the Kibana tab to add steps for viewing the lifecycle of a data stream in Streams.

• Manage a data stream -- updated to add a new section about managing data streams in the Streams UI.

• Tutorial: Migrate ILM managed data stream to data stream lifecycle -- updated to add a note about the ability to switch between ILM and data stream lifecycle in the Streams area in Kibana.

---

Not sure about the impact on these topics:

• Manually apply a lifecycle policy to an index -- I was considering updating this procedure, but I'm not sure anymore because it seems to mostly refer to applying an ILM policy to standalone indices, and not data streams (so the streams feature wouldn't really apply).

• Manage the lifecycle policy for integrations data -- not sure how this page would be affected.

[github-actions]

🔍 Preview links for changed docs

• manage-data/data-store/data-streams.md
• manage-data/data-store/data-streams/failure-store.md
• manage-data/data-store/data-streams/manage-data-stream.md
• manage-data/data-store/data-streams/modify-data-stream.md
• manage-data/data-store/index-basics.md
• manage-data/lifecycle/data-stream/tutorial-data-stream-retention.md
• manage-data/lifecycle/data-stream/tutorial-migrate-ilm-managed-data-stream-to-data-stream-lifecycle.md
• manage-data/lifecycle/data-stream/tutorial-update-existing-data-stream.md
• manage-data/lifecycle/index-lifecycle-management/policy-view-status.md

[kilfoyle]

"A stream directly corresponds to a data stream."

Assuming that a stream isn't just an alias for a data stream, I wonder if there's something more precise that we could say. For example, Each stream on the **Streams** page has a one-to-one mapping with a data stream., or something like that.

[kilfoyle]

We can ignore this one for now, since we discussed it, and I understand that what you have here is in sync with with what we have on the Observability docs. :-)

[yetanothertw]

Sure, but let's keep this comment open -- we might be able to think of a more intuitive way to convey this.

To build upon your suggestion, maybe we can say something like:
Each stream maps directly to an {{es}} data stream. or Each stream represents a specific {{es}} data stream.