chore: handle 408 error and show message [gh-824]

[nahuelon]

I hereby confirm that I followed the code guidelines found at engineering guidelines

Affected Components

• CLI
• Create CLI
• Test
• Docs
• Examples
• Other

Notes for the Reviewer

This PRs makes use of a response axios interceptor to catch 408 errors and print a user-friendly message.

I tried to add unit-tests for axios requests and interceptors here, but I had to __mocks__ axios resulting in issues with the e2e tests. That's why I moved the interceptors handler to separated functions to see if I could spyOn or mock them (without success).

TODO: try to test interceptors. FYI, mocking axios worked to test request but it require some E2E tests adjustments.

Resolves #824

New Dependency Submission

[clample]

The interceptor changes look good to me 👍

I'm not sure about the runtimes e2e test. We'll need to update the snapshot whenever we update runtimes. Could you move it out of this PR since it doesn't seem needed to handle the 408 issue?

[umutuzgur]

LGTM