feat: Add segmentation GVI, refactor scoring images

[dragonejt]

Notes

• Closes #10
• Should output_file Path be a required argument or an option with a sensible default?

Changes

• Add PyTorch and HuggingFace Transformers for the segmentation GVI method
• Add output_file as argument to assign_images script
• Rename assign_gvi_to_points to score_images
• Add ScoringMethod interface and ScoringSelector enum
• Add PixelCounting GVI scoring method which implements ScoringMethod, uses Treepedia pixel counting method
• Add Segmentation GVI scoring method which implements ScoringMethod, uses mask2former model from huggingface

Testing

• Running script with both segmentation and pixel counting methods produced scores in the geodataframe

[danbjoseph]

• i was able to run a successful segmentation. thanks for this @dragonejt ! 🎉
• there was comment on the issue about "do we want to divide the image into 4 images with 90 degree field of vision instead of 1 image with 360 field of vision before the segmentation step?" - was that considered in this PR? or are we just ingesting the source image as is?
• i think we can deal with the question about a default output_file in a different PR? i logged it as #58
• can you do at least a partial update to the docs in the README as part of this PR? can you note which category(ies) from the output are being saved for the value? can you link to the mask2former page on huggingface?
  • related to the category(ies) there's this comment from #10 (i didn't copy over the image being referenced): "see the sample segmented image above. there's a more pastel green (grassy looking area) and a more neon green (appears to be mostly trees). confirm the different possible labels related to vegetation (there are at least 2)."
• can we have an option flag to save out the segmentation results? same folder as the images, same filename with maybe "_segmentation_YYYYMMDD" appended? however, StreetView-NatureVisibility does the images side-by-side in one file and shows all the categories. ours would just the segmentation image by itself and it would be just 2 colors for vegetation and not-vegetation (or even 1 color, green for vegetation and then transparent for the null?). this request can also be logged as an issue and done after merging this PR.

[dragonejt]

Hey Dan!

• We are currently ingesting the image as-is from the JPEG format. No modification has been done, I believe.
• Sure output_file can be in a different PR. Do you want me to revert the current output_file changes then (that make it more similar to create_points.py)?
• I'll add README pages shortly.
• I can also take a look at saving the segmentation images, though I agree that it would probably be best put in a separate PR.

[danbjoseph]

• For...

  Do you want me to revert the current output_file changes then (that make it more similar to create_points.py)?

...I don't fully understand the 2 options being offered.

• I've logged #59 for the future.

[dragonejt]

Previously the script determined the output file path on its own instead of accepting a CLI argument, do we want to revert back to determining its own output file path for now?

[danbjoseph]

Previously the script determined the output file path on its own instead of accepting a CLI argument, do we want to revert back to determining its own output file path for now?

ah, no thanks. i like inputting the file path.

[ioalexei]

I'm taking a look at this to work on #59 - I can get it to work with the PIXELS argument, but running with SEGMENTATION causes my session to crash. Any suggestions for how I can identify the cause?