Evaluate lazy functions in autoscaling launch config

Instead of just copying an autoscaling launch config, first resolve any
lazily-evaluated functions by calling function.resolve(). This also has
the same effect as doing copy.deepcopy() for our purposes, so there is no
need to do both.

Change-Id: I5621c9bd1ef7686f5cf321e39e1a457f31d0783d
unit tests: Always resolve static functions

In some unit tests we were passing data to handle_update() that had not
been passed through Stack.resolve_static_data() and getting away with it
because it contained only runtime functions. With the move to only one
kind of function, this is no longer sufficient.

Change-Id: I08b968b2a83fd3c1f0af97e62ea4745c87c24652
Merge "Evaluate lazy functions in autoscaling launch config"
Merge "unit tests: Always resolve static functions"