Add parsing of run summary files
Summary
The information about the calibration runs and pointing can be extracted from the run summary ecsv file. An example of such file is below:
# %ECSV 0.9
# ---
# datatype:
# - {name: run_id, datatype: int64}
# - {name: n_subruns, datatype: int64}
# - {name: run_type, datatype: string}
# - {name: ucts_timestamp, datatype: int64}
# - {name: run_start, datatype: int64}
# - {name: dragon_reference_time, datatype: int64}
# - {name: dragon_reference_module_id, datatype: int16}
# - {name: dragon_reference_module_index, datatype: int16}
# - {name: dragon_reference_counter, datatype: uint64}
# - {name: dragon_reference_source, datatype: string}
# delimiter: ','
# meta: !!omap
# - {date: '2021-08-02'}
# - {lstchain_version: 0.7.3}
# schema: astropy-2.0
run_id,n_subruns,run_type,ucts_timestamp,run_start,dragon_reference_time,dragon_reference_module_id,dragon_reference_module_index,dragon_reference_counter,dragon_reference_source
5443,68,DATA,1627944801469151181,1627944499000000000,1627944801469151181,90,0,4469150900,ucts
5444,105,DATA,1627945656339920509,1627945359000000000,1627945656339920509,90,0,2339920200,ucts
5445,5,DRS4,1627947089335080765,1627946789000000000,1627947089335080765,90,0,5335080500,ucts
5446,5,PEDCALIB,1627947342831498400,1627947041000000000,1627947342831498400,90,0,5831498100,ucts
5447,147,DATA,1627947835931418472,1627947538000000000,1627947835931418472,90,0,2931418200,ucts
5448,154,DATA,1627949268336365534,1627948967000000000,1627949268336365534,90,0,5336365300,ucts
5449,163,DATA,1627950786826833332,1627950487000000000,1627950786826833332,90,0,3826833100,ucts
5450,157,DATA,1627952265764736427,1627951966000000000,1627952265764736427,90,0,3764736200,ucts
What is the expected correct behavior?
Expected behavior would result in automated determination of input data and auxiliary files (pointing, calibrations) location(s) from the single entry point.