update code to correspond to latest scoringutils version

[nikosbosse]

Who would have thought that this would happen so soon :)

scoringutils just got a new update which slightly changes the interface - as_forecast is now as_forecast_quantile and as_forecast_point. This PR updates the corresponding function to work with the most recent scoringutils version.

Apologies for the short notice - in the future I'll try to coordinate PRs to make sure there is no gap between the two packages.

[github-actions]

🚀 Deployed on https://669a8d3f9b863d152d4ae0e6--hubevals-pr-previews.netlify.app

[nickreich]

Looks good to me.

[nickreich]

Sorry, i spoke too soon! Can you increment the package version and add something to the NEWS.md?

[nikosbosse]

How should I increment the package version? The current version is 0.0.0.9000 which is a dev version already. And the News.md file is empty - so I think it needs a more comprehensive presentation of the package functionality first, rather than a sentence describing what the current version updates.

[nickreich]

in our experience, we've had issues where minor code changes have caused hard-to-diagnose downstream issues later. Hence my requests.

I think we should increment to 0.0.0.9001. But I see the point about it being a dev branch though. I just think we should enforce these small things.

And I re-looked at the guidelines and say that NEWS updates are maybe only necesary for user-facing changes. So maybe that change should be seen as not mandatory.

[nikosbosse]

Is hubEvals ever meant to be on CRAN? otherwise it might make more sense to have a separate dev branch and have main be the latest release?