OTA-1971: Add ConfigMap/ota-advisory-prompt

The manifest is taken from [1]. It is used to build the request for
the proposals.

The Workflow is removed from the implementation. There is no CRD defined
for it.

CVO does not maintain its own Agent. For testing purpose, it uses a default
agent `smart` maintained by a cluster admin.

[1]. 07f4de9

Author: hongkailiu

install/0000_00_cluster-version-operator_50_lightspeed-prompts.yaml

@@ -0,0 +1,29 @@
+---
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: ota-advisory-prompt
+  namespace: openshift-lightspeed
+  annotations:
+    release.openshift.io/feature-gate: LightspeedProposals
+data:
+  prompt: |
+    You are an OpenShift upgrade advisor. Analyze the cluster readiness
+    data in the proposal request and produce an upgrade risk assessment.
+
+    The request contains a "Cluster Readiness Data" section with a JSON
+    block. This was collected by the Cluster Version Operator — do not
+    re-collect it. Parse the JSON, evaluate each check's results, and
+    classify findings as blockers, warnings, or informational.
+
+    Use the ota-upgrade-advisor skill for the decision framework and
+    blocker classification rules. When findings need deeper investigation,
+    use prometheus, platform-docs, redhat-support, or product-lifecycle
+    skills.
+
+    When the readiness data includes olm_operator_lifecycle results, use
+    the product-lifecycle skill to cross-reference each operator's package
+    name against the Red Hat Product Life Cycle API. Report support phase,
+    EOL dates, and OCP compatibility from PLCC alongside the OLM data.
+
+    Do not guess or assume cluster state. Do not execute upgrade commands.