feat(execution): Exclude execution retrieval for Disabled Front50 pipelines

[christosarvanitis]

Adding an opt-in feature to exclude Execution Retrieval for Disabled Front50 pipelines. This can be configured via:

tasks:
   controller:
      excludeExecutionsOfDisabledPipelines: true #(defaults to false) 

When enabled Orca calls the Front50 with a query parameter enabledPipelines=true. Front50 responds only with the enabled pipelines of the application.

This feature aims to ease the load on the execution retrieval for applications that have a lot of pipelines and for historical reasons users dont want to delete the obsolete pipelines that are disabled.

Additionally an agent is implemented to check for unused/unexecuted pipelines per application for the past X days and disable them in Front50. This is only applicable for SQL execution repository and can be configured via:

pollers:
  unused-pipelines-disable:
    enabled: false|true #default value false
    intervalSec: 3600 #default value 3600
    thresholdDays: 365 #default value 365
    dryRun: false|true #default value true

Related Front50 change spinnaker/front50#1520

[jasonmcintosh]

As a rule, try to avoid force indexes - let the database optimize as needed as if new indexes come online or old ones get removed this would require work here.

[christosarvanitis]

Following the optimised retrieval from this PR #4804 I can revert to a simple query. What do you think?

[jasonmcintosh]

Please! Simple == better on these let the DB do it's thing... particularly if in future indexes change.