reorg lambda assets

[thecaffiend]

NOTE: some things called out here may change before this is implemented. this is meant to handle the assets at the root of the assets directory in the repo. if there are other things that have been added and are already organized, those can be left alone.

right now all the lambda assets are dumped into the repo at aessts/lambda. We have crawler triggers, etl scripts, and other notification handlers all together. we need to organize this.

this will entail not just adding in some directory hierarchy, but also changing place in the pulumi code we use the assets themselves (the usages will need to conform to the new hierarchy).