Feature/vector layer

[zacdezgeo]

What I changed

• Refactored utils.py to properly distinguish between vector and raster layers when adding them to the map.
• By the previous point, support the identify tool for vector layers by default.
• Ensured that visParams were correctly handled for raster layers to maintain expected visualization behavior.
• Fixed an issue where raster layers returned RGB values instead of elevation data when using Identify.
• Refactored utils.py to properly distinguish between vector and raster layers when adding them to the map.
• Also included a quick fix to the deprecation notice on Action Artifacts v3

How to test it

1. Run unit tests (see CI)
2. Load a DEM raster layer (e.g., USGS/SRTMGL1_003) and verify that the Identify tool returns elevation values instead of RGB.
3. Load a vector layer and use the Identify tool to ensure it returns correct feature attributes.
4. Check visualization: Confirm that raster layers still respect the visParams settings and display as expected.

Other notes

• Closes Implement Identify tool for vector layers #60
• Closes Separate Paths for Raster and Vector Layers for Map.addLayer #216
• Closes Package Action Fails using deprecated Artifact Action (v3) #218 (quick fix included here)

[zacdezgeo]

@alukach; I tried to get to type hinting, but it was already a large refactor... next iteration!

[zacdezgeo]

Also, wanted to share that I scrapped the idea of implementing a custom EarthEngineVectorProvider. It only makes sense to implement a custom provider if you want to override the default behavior from QGIS. For example, we want to use earth engine to run some custom logic on identify calls. For vector, there are no immediate needs like that; we should rely on the default behavior from QGIS.