add 2D forcing boundary and meteo to hydromt (including bug fixing for project santacruz and surat)

[xldeltares]

Working branch for Santa Cruz. This branch merged all hydromt subbranches that are underdevelopment for project Santa Cruz, plus fixes and improvements needed.

[github-advanced-security[bot]]

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

[xldeltares]

Need more investigation on if all supported forcing types (and each one of them) can be read back correctly.

Discussion point:

• What kind of update situation we should foresee? More in detail, for 1D boundary, do we expect an update for each individual locations or entirely? it is not possible to update per quantity (waterlevel/discharge), because there are dependency between location and quantity. e.g. location bnd_1 could only have either waterlevel or discharge? what about 2D boundary? for 2D meteo, I think the option is limited because we only support global.
• What kind of convention should we use for saving hydromt forcing object? points to consider: why do we need a forcing object (we do use it internally but we do not update based on these), how do we update forcing object (see above point)? What format do we need for each forcing object? e.g. 2D forcing are lines, 1D forcing are points, global forcing is a point.
• For type of forcing that we do not support, e.g. spatial varying meteo, what should we do? This question is also relevant to other update process. should we add a verification at the end of update to show how different this updated version is to the original? (a hydromt question)
• A meteo specific question: the mask file, which determines if rainfall falls within or outside the mask is not supported, because i could not think of a good way to integrate this geometry into the correct forcing data array format. How neccessary is this file? if very neccessary, how to best fit it in?

[sonarcloud[bot]]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
49 Code Smells

No Coverage information
4.8% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint