When a CRD listed in spec.customresourcedefinitions.owned in a ClusterServiceVersion does not have a description field, the Operator details page shows Not available in the CRD card body. This is misleading because it reads as if the CRD itself is not available, rather than its description being missing.

This has caused confusion - see OCPBUGS-65849 where a user saw Not available for three CRDs, verified they were running via oc get, and filed a bug thinking the operator was broken.

The Not available text comes from the default emptyMsg in SyncMarkdownView. The CRD card should use a more specific fallback like No description available to make it clear what is actually missing.

Steps to reproduce:
1. Install any operator whose CSV has owned CRDs without description fields
2. Navigate to Operators - Installed Operators - Operator details page
3. Observe the CRD cards show Not available

Expected: No description available or similar text that clarifies only the description is missing

Actual: Not available - ambiguous, implies the CRD itself is unavailable