Surface input download page additions and small issues

[masonwillman]

These are current enhancements that need made to the new surface input page in the GUI. Please add to the task list as it becomes applicable.

• A *.tif.aux.xml is generated alongside the .tif file. We should clean this up after the download is completed, or investigate if this is an error in the implementation of the DEM fetching API function.
• The download and cancel buttons on the surface input download page need icons to make them more noticeable to the user.
• For point and radius, we have an API call to fetch a DEM with those inputs. The GUI will convert point and radius inputs into lat/lon and call the bounding box API call. We should change this so if point and radius is selected, we use the correct API function.
• The time zone combo box need to update with the inputted DEM. It should be based on the time zone that the DEM is located in.

[masonwillman]

For each .tif file, GDAL will generate a *.tif.aux.xml. This provides metadata regarding the .tif file. I believe this is occuring due to our updating of the GDAL dependency from gdal-3.2.1 to gdal-3.4.1. By setting the environment variable GDAL_PAM_ENABLED=NO, I was able to stop them from generating on my system. The only references I can find for this variable are in ninjaArmy.cpp at lines 550 and 634.

Button icons were added via commit 049a2a1.

[masonwillman]

Right now, all tasks that were originally required are completed, but new needs to refactor have come up.

• The function to get the time zone information could be optimized/improved. It was originally written by the MSU capstone team, who did not have great GDAL knowledge.
• We need to expose the function SurfaceFetch::createBoundingBox function to do the conversions for the GUI, rather than implementing another method.
• Rather than a radius, we should provide a buffer x and y, and use those to display the box for the user. This will pair well with the SurfaceFetch::createBoundingBox function, as it expects the buffer in x and y. Additionally, we will need to change the GUI function SurfaceInput::computePointRadius to compute the x and y buffer.