Description

In the optimizations breakdown view, memory values are not displayed in both the "Current configuration" and "Recommended configuration" code blocks. CPU values render correctly, but memory fields show empty values with a warning icon.

Steps to Reproduce

1. Navigate to Optimizations
2. Click on any workload with recommendations
3. Observe the "Current configuration" and "Recommended configuration" cards

Actual Results

The configuration cards show:

Expected Results

Memory values should be displayed alongside their units, similar to CPU values:

limits:
  cpu: 1
  memory: 1024 MiB
requests:
  cpu: 0.5
  memory: 512 MiB

Root Cause Hypothesis

The ROS API (ros-ocp-backend) transforms memory units via transformComponentUnits in internal/api/utils.go. The API response returns memory with format: "bytes" and the raw numeric amount (e.g., amount: 1024, format: "bytes"). The UI formatting pipeline (formatValue -] unitsLookupKey -> formatOptimization) may not have a mapping for the "bytes" unit format returned by the API, causing the formatted value to be empty.

The issue affects both:

• koku-ui-mfe/src/routes/optimizations/optimizationsBreakdown/optimizationsBreakdownConfiguration.tsx
• koku-ui/apps/koku-ui-ros/src/routes/optimizations/optimizationsBreakdown/optimizationsBreakdownConfiguration.tsx

Discovery Context

Observed while validating FLPATH-3292 fixes with sample recommendation data inserted into the costonprem_ros database. The memory display issue is independent of the FLPATH-3292 performance engine fix.