In the CMEMS → dfsu example (https://dhi.github.io/mikeio/examples/dfsu/cmems_vertical_profile.html), it would be useful to:
- include the vector components uo and vo in the example workflow
- infer n_points automatically from the CMEMS grid rather than requiring it as a manual input
- add an option/function to flip the horizontal orientation of the extracted output (potentially only needed for dfs2; dfsu with lat/lon may already handle this automatically?)