Initial function state status improvements

[markpeek]

• [X] Feature

Detailed Description

When running through our examples I added the seed.yaml. Then looked at the status: hello-py | python3 | INITIALIZED | Sat Jan 1 10:59:06 PST 0000 Hmmm...initialized, let's try to run it:

$ dispatch exec hello-py --input '{"name": "Jon", "place": "Winterfell"}' --wait
[Code: 404] Function execution not found: hello-py

ok, that didn't work. Oh it goes initialized -> creating -> ready.

Issue #1: Initialized sounds like it is ready to go. Should INITIALIZED be INITIALIZING?

Issue #2: Running the function via exec, if it fails should we also look up the state to tell the user it isn't READY yet?

[berndtj]

Returning a not found/404 on exec I think is the real issue here. We should return an error indicating the function exists, but is not in a READY state yet.

I don't actually have any issue with the vocabulary used (i.e. INITIALIZED), but we need to give the users more information so they don't need any additional context.