Add check for lat long location in satellite data spatial slicing

[Sukh-P]

Pull Request

Description

For satellite data spatial slicing we currently assume that the central coordinate of interest will be in an osgb coordinate system, which is UK specific, but coordinates of interest can also be in lat long for example for sites outside of the UK this is common. This change will add a check for what coordinate system is being used in the location of interest and then use the appropriate conversion function to geostationary coords.

How Has This Been Tested?

Adding a unit test for this case and running the pipeline on a small sample of data

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have checked my code and corrected any misspellings