`StorageFallbackScheduler` return structure differs from `StorageScheduler`

[Ahmad-Wahid]

StorageFallbackScheduler.compute() does not return the same output structure as StorageScheduler.compute().
This breaks the scheduler contract and forces downstream code to special-case fallback results (While using multi-asset scheduling in simulations).

Current behavior

• StorageScheduler returns (when return_multiple=True):

  • storage_schedule
  • commitment_costs
  • state_of_charge
  • Consistent schema (name, sensor, data, unit)

• StorageFallbackScheduler returns:

  • Only storage_schedule
  • Missing commitment_costs and state_of_charge
  • Slight schema differences