refactor: Move GeosBlockExtractor from geos-posp to geos-mesh

[RomainBaville]

In the context of the code refactoring, this pr aims to:

• Move the filter in the correct folder and update import/doc
• Stop using VTKPythonAlgorithmBase as mother class of the filter
• Implement a child class of vtkExtractBlock to extract geos domain directly
• Implement a test file for the filter.

Note: A future pr will clean all the test mesh

[paloma-martinez]

Suggested change

	CellElementRegion is automatically extracted, by defaults SurfaceElementRegion and SurfaceElementRegion are empty multiBlockDataSet.
	CellElementRegion is automatically extracted, by defaults SurfaceElementRegion and WellElementRegion are empty multiBlockDataSet.

[paloma-martinez]

Suggested change

	GeosBlockExtractor is a vtk filter that allows to extract blocks from the ElementRegions from a GEOS output multiBlockDataset mesh.
	GeosBlockExtractor is a vtk filter that allows to extract the ElementRegions blocks from a GEOS output multiBlockDataset mesh.

[paloma-martinez]

Maybe a mix of the previous and the current doc, something like this ?

Suggested change

	The three ElementRegions are:
	0: CellElementRegion,
	1: SurfaceElementRegion,
	2: WellElementRegion,
	The three ElementRegions are:
	0: Volumes ( labeled `CellElementRegion` in the mesh )
	1: Faults ( labeled `SurfaceElementRegion` )
	2: Wells ( labeled `WellElementRegion` )

[jafranc]

An enum for that would make it clearer

[RomainBaville]

I use the one already existing

[jafranc]

Please add an Enum and the outer-most property
Checks from the setters could be a plus. ➕ if not too heavy

[jafranc]

An enum for that would make it clearer

[jafranc]

This I think is an enum and eventhough should be class var and not instance var :)

[RomainBaville]

It is indeed an enum and it is already defined in GeosOutputsConstants. I don't need to rewrite it.

[jafranc]

should it be accessible outside of the class ? If not then decorate it with @property

[RomainBaville]

It needs to be accessible outside of the class to get the result of the extraction

[jafranc]

If returned value is not used then maybe drop it, else maybe raise an error with diagnostic

[jafranc]

Can the setters actually check that the elements from the multiblock passed in arg are of the right type ? something following this logic

cell_type = cell.GetCellType()

# Use vtkCellTypes to get dimension
dimension = vtk.vtkCellTypes.GetDimension(cell_type)

if dimension == 3:
    print("This is a volume cell.")
elif dimension == 2:
    print("This is a surface cell.")
elif dimension == 1:
    print("This is a line cell.")
else:
    print("Unknown or unsupported cell typ

[RomainBaville]

Good idear. I have implemented a new function to get the dimension of the cells of the mesh and I test this dimension in the setters. It also test taht the mesh is a vtm

[alexbenedicto]

Suggested change

	def AddGeosElementRegionsBlockIndex( self, elementRegionId: int ) -> None:
	def AddGeosElementRegionsBlockIndex( self: Self, elementRegionId: int ) -> None: