fix: go for forecast method instead of predict in ets

[Lopa10ko]

This is a 🐛 bug fix.
Related to api_ts_forecasting_example integration test failure.

• Change predict logic by calling forecasting method instead of a predict one in ExpSmoothingImplementation (27315b2)
• Make sure that this resolves the issue with that kind of pipelines by running saved troubled pipelines locally
• Remove obsolete custom message logging level (da4fc93)

related to #1297, but not closing it since there are various types of troubled pipelines
closes #1300

[docu-mentor]

👋 Hi, I'm @docu-mentor, an LLM-powered GitHub app
powered by Anyscale Endpoints
that gives you actionable feedback on your writing.

Simply create a new comment in this PR that says:

@docu-mentor run

and I will start my analysis. I only look at what you changed
in this PR. If you only want me to look at specific files or folders,
you can specify them like this:

@docu-mentor run doc/ README.md

In this example, I'll have a look at all files contained in the "doc/"
folder and the file "README.md". All good? Let's get started!

[Lopa10ko]

[github-actions]

All PEP8 errors has been fixed, thanks ❤️

Comment last updated at

[nicl-nno]

На проблему с ets хорошо бы тест добавить. Хотя бы для какого-то конкретного пайлпайна.

[Lopa10ko]

На проблему с ets хорошо бы тест добавить. Хотя бы для какого-то конкретного пайлпайна.

e43412e