105 update meshkernel api calls to version 300

[veenstrajelmer]

Issue addressed

Fixes #105

Explanation

There were major hydrolib-core changes to facilitate meshkernel 3.0.0. Actually it was based on meshkernel 2.0.2, so it makes sense that it could not work with meshkernel 2.1.0. The hydrolib-core PR contains all changes: https://github.com/Deltares/HYDROLIB-core/pull/574/files

Checklist

• Updated tests or added new tests
• Branch is up to date with main
• Tests & pre-commit hooks pass
• Updated documentation if needed
• Updated changelog.rst if needed

Actual checklist:

• green testbank with hydrolib-core branch 569-bumping-meshkernel-version-to-latest-v300
• remove mesh1d_set where possible, should be done by hydrolib-core when needed
• Check amount of nodes/edges/faces in mesh1d, mesh2d and links in resulting grid. Check whether the resulting grid is not duplicated (double generated) and update hydrolib-core testbank if needed.
• move hydrolib-core dependency from branch to release (Integrate MeshKernelPy >=3.0.0 HYDROLIB-core#574) (envs and toml)
• move xugrid dependency from branch to release (updated meshkernel apicalls to meshkernel v3 xugrid#171) (envs and toml)

[xldeltares]

Hi @veenstrajelmer , I had a quick check of the PR. both the changes and the model generated seems fine.

[xldeltares]

Hi @veenstrajelmer, just found a new error from hydromt-delft3dfm python 3.9 test bench: "ImportError: cannot import name 'UnionType' from 'types')" when calling from meshkernel.meshkernel import MeshKernel. Do you know if that is because meshkernel does not support python 3.9 anymore?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
2 Code Smells

No Coverage information
0.0% Duplication

[xldeltares]

review is OK!