fix: use custom type pydantic class to wrap ndarray and avoid validation problem

[frodehk]

ECALC-965
fixes #482

Have you remembered and considered?

• I have remembered to update documentation
• I have remembered to update manual changelog (docs/docs/changelog/next.md)
• I have remembered to update migration guide (docs/docs/migration_guides/)
• I have committed with BREAKING: in footer or ! in header, if breaking
• I have added tests (if not, comment why)
• I have used conventional commits syntax (if you squash, make sure that conventional commit is used)
• I have included the Jira issue ID somewhere in the commit body (ECALC-XXXX)

Why is this pull request needed?

When users are using eCalc directly on CLI, they will be met with a few warnings that will most likely be difficult for them to understand, so we should either handle them or silence them.

What does this pull request change?

The problem is caused by sending numpy.ndarrays directly into pydantic, giving validation problems. Avoiding the problem using custom type PydanticNDArray to wrap numpy.ndarray, and use that type instead of numpy.ndarray directly.

A more long term solution is to return List and Float from core.

Issues related to this change:

https://equinor-ecalc.atlassian.net/browse/ECALC-965?atlOrigin=eyJpIjoiNjUxNmVlMmY4ZWEyNGU5YzhmN2RhM2MyZTY0NGE2OWYiLCJwIjoiaiJ9

[TeeeJay]

great! please also make a pathc for 8.15 release :) and make sure you use conventional commit syntax as well as referring correctly to jira issue in commit message :)