Results are ALWAYS sorted by obligated amount, descending; the endpoint
accepts no sort or order parameters. (Earlier releases exposed sort/order
here, but the API silently ignored them: the advertised default of
period_of_performance_start_date was never the actual ordering. Round 10
audit finding.) For date-ordered children use get_idv_children(), whose
endpoint does honor sort/order.

hide_edge_cases=True filters out child awards missing obligated/awarded
amounts or end dates.