Unify usage of CRS object

[Jaapel]

Kind of request

Changing existing functionality

Enhancement Description

Currently, crs in the code can be a str, int or pyproj.CRS object.
HydroMT should be flexible in parsing, but strict in internal code. This is not yet the case. We should use the same CRS object in all internals.

Use case

General Maintainance effort and readability of the code will benefit from these changes.

Additional Context

No response

[DirkEilander]

We already tried to unify our internal representation of CRS a while back. Before we used by the rasterio and pyproj CRS objects interchangable, now internally all CRS objects are pyproj object right? Can you point to an example where you would like to see more additional changes?