Set run_as for analysis-projects based on if it's for "production"

The idea behind this is so that users can create AnPs for imported (non-production) datasets where builds will run as them rather than the standard apipe-builder.
Having an enumerated property would be similar to allowing the user to set run_as during creation directly.  That might be an option, but initially I had concerns about allowing anyone to set run_as=cle.  However, the isolation of CLE data to cle protected disk groups means, models using CLE data incorrectly will not run and a user attempting to run research/production data as the cle user will also fail.  We seem to be discussing three options: 1.) Set the run_as during create 2.) is_cle and is_production, ad hoc is assumed when neither is set 3.) enumerated environment property.

I was still wary of option 1 since cle models could be setup in error.  The models should not run, but we would need to find those errors and clean them up periodically.

Options 2 was simply a continuation of the is_cle flag.  All LIMS workorders will have a is_cle binary property as well.  I believe we were trying to maintain some consistency.  

For option 3, @tmooney can correct me if I'm wrong, but I assume CQID could resolve the is_cle flag on workorders and set an environment property to 'cle'.  My concern is the behaviour for 'ad hoc'.  I could see us having many environments in the future (multiple ad hoc) so option 3 might work.  It could encode many environment variables and settings rather than the single run_as setting/property.