changes in cal line frequency parameters

@ling.sun reports the error below when running code in uncertainty.py.

uncertainty.py", line 992, in compute_response_uncertainty
    sensing_line_freq = self.darm.calcs.cal_line_sens_pcal_frequency
AttributeError: 'Model' object has no attribute 'cal_line_sens_pcal_frequency' 

I've also run into a similar problem in calcs.CALCSModel.compute_epics_records().

In [24]: calcs_obj.compute_epics_records()
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[24], line 1
----> 1 calcs_obj.compute_epics_records()

File ~/repos/pydarm/pydarm/calcs.py:863, in CALCSModel.compute_epics_records(self, endstation)
    861 f_pum = self.calcs.cal_line_sus_pum_frequency
    862 f_tst = self.calcs.cal_line_sus_tst_frequency
--> 863 f_pcal1 = self.calcs.cal_line_sus_pcal_frequency
    864 f_pcal2 = self.calcs.cal_line_sens_pcal_frequency
    865 f_pcal3 = self.calcs.cal_line_high_pcal_frequency

AttributeError: 'Model' object has no attribute 'cal_line_sus_pcal_frequency'

After taking a closer look, it seems that this is due to cal_line_sus_pcal_frequency, cal_line_sens_pcal_frequency, and cal_line_high_pcal_frequency being renamed to cal_line_pcal1_frequency, cal_line_pcal2_frequency, and cal_line_pcal3_frequency, respectively, in the pydarm parameter set. For example see the old 20190416 ini vs the current ones (0125 & "new" cmd ini).

The appropriate sections of pydarm need to be adjusted to match the new naming convention.