(core): pull angular-cron-gen library internally

* pull angular-cron-gen library internally to deck to fix several issues
with the library.
* the latest version of the library will not allow angular expressions
for the new `template-url` property as it uses the `templateUrl`
function which executes before the scope is initialized so any
scoped property value is not accessible.  this means that our template
value set via a controller property is not accessible.  this is a
long-standing issue [in the core library](angular/angular.js#2895)
and it doesn't look to be fixed anytime soon.
* an hourly cron trigger set in the UI to execute start at a specific
time actually generates a daily cron expression so the portion of the
hourly cron trigger that allows starting at a specific time was
removed from deck's cron picker template.
* the regex used by the library to match hourly cron expressions was
incorrectly matching daily cron expressions which was resulting the UI
displaying `hourly` instead of `daily` in the select so the regex for
hourly was fixed to properly test for matching hourly cron expressions.

Author: icfantv

app/scripts/modules/core/pipeline/config/triggers/cron/cronPicker.html

@@ -41,30 +41,6 @@
           hour<span ng-if="state.hourly.every.hours> 1">s</span>
         </div>
       </div>
-      <div class="row">
-        <div class="col-md-12">
-          <input type="radio"
-                 value="specific"
-                 ng-change="regenerateCron(state)"
-                 ng-model="state.hourly.subTab"
-                 name="hourly-radio">
-          At
-          <select class="form-control input-sm"
-                  ng-change="regenerateCron(state)"
-                  ng-model="state.hourly.specific.hours"
-                  ng-options="hour as padNumber(hour) for hour in selectOptions.hours"
-                  ng-required="state.activeTab === 'hourly' && state.hourly.subTab === 'specific'">
-          </select>
-          :
-          <select class="form-control input-sm"
-                  ng-change="regenerateCron(state)"
-                  ng-model="state.hourly.specific.minutes"
-                  ng-options="minute as padNumber(minute) for minute in selectOptions.minutes"
-                  ng-required="state.activeTab === 'hourly' && state.hourly.subTab === 'specific'">
-          </select>
-          <system-timezone></system-timezone>
-        </div>
-      </div>
     </div>
     <div ng-if="state.activeTab === 'daily'">
       <div class="row">

app/scripts/modules/core/pipeline/config/triggers/cron/cronTrigger.module.js

@@ -6,7 +6,7 @@ import {UUIDGenerator} from 'core/utils/uuid.service';
 import './cronTrigger.less';
 
 module.exports = angular.module('spinnaker.core.pipeline.trigger.cron', [
-    require('angular-cron-gen'),
+    require('core/utils/cron/cron.js'),
     require('../trigger.directive.js'),
     require('core/serviceAccount/serviceAccount.service.js'),
     require('./cron.validator.directive.js'),
@@ -39,5 +39,4 @@ module.exports = angular.module('spinnaker.core.pipeline.trigger.cron', [
     this.cronOptions = {
       templateUrl: require('./cronPicker.html'),
     };
-
   });