Add mesh_stats checks and field_operations features

[alexbenedicto]

Closes #50

Followed the previous work on PR #19 and closes #19.

Two features added:

• field_operations: provides a tool to copy and create new fields on a .vtu file using a VTK file as input that contains PointData or CellData. This VTK file can either be a .vtu, .vtm or .pvd file as long as the complete geometry corresponds to the one of the .vtu file that will receive this data.
• mesh_stats: provides a summary of mesh statistics on geometry, topology and properties painting. This is a starting point for this feature that will be enhanced to check later mesh quality.

[bd713]

I would move the "local" imports at the end

[bd713]

From the comment, it seems like we expect exactly 2 str in the tuple. Would something like list[ tuple[ str, str ] ] work?

[bd713]

Looks like a great opportunity to use your support_construction defined at L30.

[bd713]

It's tempting to have a seperate function that would return the number of elements, especially if the support_choices list is intended to grow in the future.
That would avoid changing the code everywhere it is repeated, like L209.

[bd713]

In the doc string, "returns an array..."

[bd713]

For readability and as you did L80, we could do:

Suggested change

	for i in range( result.number_cell_types ):
	logging.info( f"\t{result.cell_types[ i ]}\t\t({result.cell_type_counts[ i ]} cells)" )
	for cell_type, type_count in zip(result.number_cell_types, result.cell_type_counts ):
	logging.info( f"\t{cell_type}\t\t({type_count} cells)" )

[bd713]

Suggested change

	for field_name, validity_range in data.items():
	is_valid: bool = validity_range[ 0 ]
	min_max: tuple[ float ] = validity_range[ 1 ]
	for field_name, (is_valid, min_max) in data.items():

[bd713]

Suggested change

	if options.write_stats:
	if is_valid_to_write_folder( options.output_folder ):
	if options.write_stats and is_valid_to_write_folder( options.output_folder ):

[bd713]

Suggested change

	for i, sub_grid in enumerate( sub_grids ):
	for name, value in sub_grids_values[ i ].items():
	for sub_grid, sub_grid_value in zip(sub_grids, sub_grids_values):
	for name, value in sub_grid_value.items():

[bd713]

At some point, could maybe be moved to the vtk utils ?

[alexbenedicto]

The mesh-doctor features developed here can be readded in future PR to create vtk filters for mesh-doctor.