setup a generic reporting job for product-ci

[Aleksandra Fedorova]

At this moment we have the following structure:

8.0.all
|
---> 8.0.all-Testrail
---> fuel_ci-status_reports
---> trigger-external-events

See https://github.com/fuel-infra/jenkins-jobs/blob/master/servers/new-product-ci/8.0/all.yaml

All three jobs are specific for our product infrastructure and are not usable for third-parties.

We need to reconfigure jobs to have a implementation agnostic reporting job.

8.0.all
|
--> send-reports
       |
       ---> 8.0.all-Testrail
       ---> fuel_ci-status_reports
       ---> trigger-external-events

This way we don't need to store reporting configuration in the ISO building job itself. We can store it separately and override when needed

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/13654
Submitter: Igor Belikov <email address hidden>
Branch: master

Commit: 2768f6aaf73acbfe55bafdf7ff3765d71d9aaabf
Author: Aliaksei Cherniakou <email address hidden>
Date: Mon Nov 9 09:06:40 2015

Implementing agnostic send_reports job

It does nothing except triggering reporting jobs
specific for internal product infrastructure.
One can be disabled during generation by setting
send_reports_disabled property in global.yaml to true.

Related-Bug: #1510094
Change-Id: Idbdbe8aea43397f24cc2df4a5535a8fff707d902