docs(konveyor): add the Alauda support for Konveyor installation guide

[SuJinpei]

The certified Alauda support for Konveyor package is going GA, and its marketplace Overview links
to solutions/ecosystem/konveyor/Konveyor_Installation_Guide.html — which did not exist. This adds
it, following the Knative / Nacos / OpenSearch guide convention.

New: ecosystem/konveyor/Konveyor_Installation_Guide.md

The guide leads with storage planning, because that is what actually blocks installs. The
platform asks for two ReadWriteOnce volumes; hand-written YAML that omits the size fields inherits an
upstream default of 100Gi for the file store, which many clusters cannot bind. The console form
is prefilled with smaller tested values (5Gi / 10Gi) and the guide says so explicitly rather than
leaving the discrepancy to be discovered.

Known limitations are stated up front:

• Authentication cannot be enabled in this release (feature_auth_required must stay false) —
  the Keycloak images it needs are published for amd64 only and are not shipped with the package.
• The AI-assisted migration feature is not available, for the same reason.
• ui_ingress_class_name defaults to nginx, which many clusters do not run.
• No upgrade path from the older community konveyor-operator catalog entry (0.6.0-beta.1) —
  this is a separate, newly published package.

Uses the factory:auto:* marker convention so later releases regenerate only the version and
limitation slots, leaving the prose human-owned.

Corrected: How_to_Use_Konveyor.md

That page describes the older community entry and actively contradicts the certified package — it
recommends feature_auth_required: true, rwx_supported: true and a 100Gi bucket. Rather than
rewrite content that is still correct for its own audience, it now states which package it applies
to, and carries warnings at the two places that would break someone following it on the certified
package (the Tackle example and the KAI section), each pointing at the new guide.

Conventions followed

• en only. The zh mirrors are produced by the translation pipeline from the en sources (tracked
  via sourceSHA) and are not committed by hand.
• No id: in the new file's frontmatter — add_id.sh allocates it from the CRM by H1 title on
  merge to main, and skips any file that already has one.