add more details to eol/eos runtimes

[thomas-tacquet]

Added some details to warn about EOL and EOS

Result in shell :

Using credentials from system environment
Runtime undefined is in End Of Support. It is no longer possible to create a new function with this runtime; however, functions that already use it can still be updated.
Note : Node 17 reached end of security support 1st June 2022, please upgrade to Node 16 or Node 18

Runtime lifecycle doc : https://www.scaleway.com/en/docs/compute/functions/reference-content/functions-lifecycle/#available-runtimes

           
Creating function first...
Environment: darwin, node 16.14.0, framework 3.19.0, plugin 6.2.2, SDK 4.3.2
Docs:        docs.serverless.com
Support:     forum.serverless.com
Bugs:        github.com/serverless/serverless/issues

Error:
Error: message : Node 17 reached end of security support 1st June 2022, please upgrade to Node 16 or Node 18, error : rpc error: code = InvalidArgument desc = runtime reached end of support, could not create new functions

[Shillaker]

Is it possible to add an integration test to create a function with an EoS runtime and check it returns the right message?

We'll have to periodically update it to match our current list of EoS runtimes. This might get annoying but it's probably worth the effort.

I can't implement e2e tests for EOL/EOS before the release of updated runtimes status.