Plan shows lambda being rebuilt when previous apply was done on different machine

[jniesen]

Because one of the keepers for random_id.zip is an absolute path to the source directory for the lambda function code the random_id is regenerated between when applying on one system and then on another where the path can be different. This causes a cascading affect where all of the resources that depend on the random id are marked for change or recreation.