Fix: Show warning instead of failing the run

[cino]

Description:
As there are currently issues with the caching service which is breaking workflows using the caching I suggest we change the workflow to only fail when there are configuration errors. When anything else goes wrong in the workflow, like a 503 error there should be a warning but let the workflow run continue.

Having caching available or not should not be breaking the workflow, instead, just continue as if there is no cache.

Related issue:
#516

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[cino]

Check dist action was failing due to me not committing the dist files, however, I think someone should update the contributors.md

[IvanZosimov]

Hi, @cino 👋 ! Thank you for your contribution a lot! Unfortunately, we decided to implement such error handling by ourselves on another let's say deeper level. We really appreciate your effort and willingness to help! ❤️

By now I'm going to close this PR, if you have any questions or suggestions feel free to ping us.