[Docs] De-emphasize Docker. Explain that any OCI container daemon will work.

[ppiegaze]

Description

Currently in the docs we specify that users should install Docker to enable deploying Flyte workflows on a local cluster. In fact any OCI-compatible container engine will do (options include Podman, RKT and LXD, there are others).

While most user will, in fact, use Docker, we should be accurate and explain that other engines will also work.
We should rewrite the sections that mention Docker. The Getting Started section should tell the whole story in detail, while saying "for example, Docker". Other mentions of Docker can be adjusted slightly. Some thing like "container engine (e.g., Docker)"

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[neverett]

Addressing this in flyteorg/flytesnacks#1266