Bumping meshkernel version to latest (v3.0.0)

[ahmad-el-sayed]

What is the need for this task.
Currently, HYDROLIB-core uses meshkernelpy 2.0.2, as configured here. A minor version 2.1.0 was released last July and version 3.0.0 is planned next week.

What is the task?
Is there interest in bumping the version to 3.0.0?

Benefits:

• improvements in performance
• new features
• bug fixes

These has been API changes. The MeshkernelPy team can gladly assist.

[veenstrajelmer]

It is necessary to include the API changes from meshkernel 3.0.0 and use that as a minimal required version.

Fundamentally, these things should be updated:

• hydrolib-core requires meshkernel^2.0.0 (so <3.0.0), update to meshkernel^3.0.0 after updates
• hydrolib-core calls mk.DeleteMeshOption.ALL_FACE_CIRCUMCENTERS upon hydrolib-core import, update to new meshkernel.DeleteMeshOption.INSIDE_NOT_INTERSECTED.
• hydrolib-core calls mk.MeshKernel(is_geographic=is_geographic) upon mdu = hcdfm.FMModel()
• update DeleteMeshOption everywhere
• update to is_geographic to projection everywhere (including enum instead of bool)
• delete poetry.lock necessary? (wait until meshkernel 3.0.0 is released)

However, there is more to it I cannot completely oversee yet:

• HYDROLIB-core currently runs the github testbank with meshkernel 2.0.2 due to poetry.lock. I noticed in a local test (meshkernel 2.1.0) that the deprecated meshkernel.Mesh2dFactory() is called in tests/dflowfm/test_net.py.
• there are many functions that use meshkernelpy API's that were changed. A brief overview is available in this issue and it's comments: update meshkernel api calls after new release dfm_tools#563
• hydrolib testbank is now green, but hydromt_delft3dfm uses hydrolib-core for mesh generation and the testbank fails: 105 update meshkernel api calls to version 300 hydromt_delft3dfm#109 >> probably some things were damaged in this PR