GRIB support for saving time increment for time aggregated data (PDT4.8)

This PR enhances the existing code for saving data in PDT 4.8. As well as refactoring the code it adds support for parsing and saving the cell_methods on cubes to determine the interval (e.g hourly or daily) of the data that has been summed/averaged/...
Should you be using `grib_set_long` for a float/double anyway?

If the use of `grib_set_long` is correct then wouldn't `time_range_in_hours` be a long integer (np.int64)? Conversely if `time_range_in_hours` is a float/double then shouldn't `grib_set_double` or similar be used?

Or perhaps I'm misunderstanding.