Move Known Issues docs to Release Notes section

[dfarrell07]

When we want to talk to a user about a release, we typically want to cover both new features and any known issues. It would make more sense to group those together.

We could mention when KIs are introduced in per-release sections and also have a section for the KIs in the current release. We could also have a KI section for each active release branch.

[dfarrell07]

It seems to me we have a few types of KI, and that different types might fit best in different places.

Currently, many of our KIs are long-term and apply to all current and likely-future versions of Submariner. Example:

• The oldest Kubernetes version for which Submariner is known to work is 1.19 (1.21 for Service Discovery).

There are some that apply to all current versions, but will likely not apply to near-future versions. Example:

• Submariner does not support IPv6-only setups. On dual-stack setups, it only allocates IPv4 addresses.

There could also be new KIs that apply to only recent versions of Submariner, not older ones.

So we need:

1. A place for documenting long-term KIs that apply to all of SubM and are not likely to be fixed anytime soon. This might should live at the current Operations/Known Issues location.
2. A place for documenting KIs apply to specific releases. I don't think we want to repeat every KI in every release, but we need a way for a user to easily tell which KIs apply to a given release.
3. Maybe a way to think about KIs by release stream, as that's how KIs are typically fixed and how users typically do updates.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further
activity occurs. Thank you for your contributions.