chore!: ensure power to fuel values are strictly increasing

[frodehk]

BREAKING CHANGE: Do not allow power to fuel functions that are not strictly increasing or decreasing.

ECALC-1511

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?

Power to fuel function (ELECTRICITY2FUEL): The input data set is sorted by the value in the x-column in eCalc before plotting. eCalc further uses the sorted power-to-fuel function for calculations: This can lead to over-estimate fuel consumption at certain power consumptions. This is typically if the user input is not strictly increasing.

What does this pull request change?

Give resource validation error if power to fuel is not strictly increasing.

Issues related to this change:

https://equinor-ecalc.atlassian.net/browse/ECALC-1511?atlOrigin=eyJpIjoiZWJiODA5YzllZDkxNDQ0ZDhjMWU1M2YyMGM1N2E2YzAiLCJwIjoiaiJ9