Consider moving RasterTiler class to the viz-workflow repo

[robyngit]

Consider moving the entire RasterTiler.py class to the viz-workflow repo, and remove it from this repo. Advantages:

• Stay consistent with viz-3dtiles repo
• pdgstaging not a dependency
• keep viz-raster generic (just creates rasters from vectors, independent from staging)

This would also make it easy to, for example, read in a staged vector file as a geodataframe only once, deduplicate only once, then pass that geodataframe to be converted to both 3dtiles and rasters. All of this could be coordinated in the viz-workflow repo.

See discussion here

[robyngit]

@rushirajnenuji @alonakos does this idea still make sense with your argos & kubernetes work? If not, please feel free to close it.

[alonakos]

@robyngit This actually would help a lot with my current work too, because rn, I am calling the WMTS Generator in the RasterTiler.py. Ideally, we want to be able to call WMTS Generator from any part of the workflow. So if we move RasterTiler.py to the viz-workflow repo from viz-raster it might simplify things. One issue is I hope we can still access all the arguments and configurations we need. @rushirajnenuji Do you know if that would be a good idea? I could take this ticket since I am already working with RasterTiler