Add configurable timeouts for complex awaiters

[lblackstone]

Allow the default timeout for each complex awaiter to be
overridden by setting the pulumi.com/timeoutSeconds
annotation.

Fixes #243

[metral]

LGTM. It seems here, that the idea is for each component to have its own declared timeout as an annotation. Have we tested this with multiple components who are dependent on each other, each w/ their own timeouts? e.g. A Deployment that depends on a Service, both annotated with differing timeouts?

[lblackstone]

@metral I didn't specifically test it, but the configurable timeout doesn't change the existing semantics. All of these awaiters already have default timeouts set, and the result of a timeout is a reported failure to the CLI. Subsequently running an update/refresh after a timeout would work as usual.

[hausdorff]

A little late to the party, but would be nice to have tests for this.

[naveensrinivasan]

How do we modify the default timeout? I didn't see any doc how to do it?

[lblackstone]

There's currently no way to modify the default timeout, but you can set overrides on individual resources with the timeoutSeconds annotation. See https://blog.pulumi.com/improving-kubernetes-management-with-pulumis-await-logic for example usage