Review and document ways components in puppet-runtime are linked and configured

It's difficult to quickly get an idea of what our C++ and ruby build environments in puppet-runtime look like, since special cases are distributed throughout individual components. Before we can clean this up, we need someone to review the existing configuration settings (flags, environment variables, etc.) in the component files and identify:

• Patterns of configuration that can be migrated to project definitions
• Patterns of configuration that can be migrated to platform definitions

The output of this ticket should be:

• A set of new tickets around making these migrations
• Another new ticket, blocked on the the migration tickets, which will apply this same process to puppet-agent after puppet-runtime.