functions: fix route timeout

[ucirello]

Fix #339

[denismakogon]

So, here the thing, we need to have persisted models definitions out of code in order to have good enough user experience during upgrades from version X to version Y.

Another question, if i would create a route before this patch and then will upgrade functions API up to this patch how this code will handle cases where model wouldn't have Timeout attribute.

Along with that, this code doesn't actually validate if Timeout fits integer range.

Mentions: https://open-iron.slack.com/archives/functions/p1480362602001126

[ucirello]

So, here the thing, we need to have persisted models definitions out of code in order to have good enough user experience during upgrades from version X to version Y.
Another question, if i would create a route before this patch and then will upgrade functions API up to this patch how this code will handle cases where model wouldn't have Timeout attribute.

Ideally, we shall have stable model definition by v1, and from there backward compatible changes only. This hasn't been discussed yet. We are still in the Alpha cycle where we all expect things to break often.

Currently, routes whose configuration has Timeout zero, will no longer have any timeout. Coding something around expected timeouts is a big mistake. Thus, it should impact no one doing it right - and it will create a minor nuisance for those using it.

Along with that, this code doesn't actually validate if Timeout fits integer range.

Indeed it doesn't. But also this PR is WIP. I shall align integer sizes once I regenerate client libraries.

[pedronasser]

60 or 30 seconds?

[ucirello]

it should actually be 30, because that what it was before. I am reducing the default in the other package.

[ucirello]

done