Reorganize into core and extra profilers

[tnem]

With the goal of modularity across:

• Different OSes
• Different sets of functions to profile

I've broken things up into the following layout:

• Core profiler class, largely a stub
• Separate profiler classes for base and extended posix
• Launcher, pulls in the serverless environment to determine what profiler to run
• Separate utility file for common features
• Don't break things out into separate files unless we've established that it'll actually be reusable

This will allow for easy expansion with:

• Adding things to one or more profilers (the profiler class can just include the new code) to prevent the profiler files from growing unboundedly
• Giving guidelines for adding new profilers (windows systems, etc)

[tnem]

@andrewkrug