Remove Fuji Jobs in preperation for Geneva Release

[lranjbar]

Signed-off-by: Lisa Rashidi-Ranjbar lisa.a.rashidi-ranjbar@intel.com

PR Checklist

Please check if your PR fulfills the following requirements:

• [X] The commit message follows our guidelines: https://github.com/edgexfoundry/ci-management/blob/master/.github/CONTRIBUTING.md

• [ ] Tests for the changes have been added (for bug fixes / features)

• [ ] Added labels

  PR Type

  What kind of change does this PR introduce?

• [ ] Bugfix

• [ ] Feature

• [ ] Code style update (formatting, local variables)

• [ ] Refactoring (no functional changes, no api changes)

• [ ] Documentation content changes

• [X] Other... Please describe:

JJB Template Changes to remove Fuji jobs. In cases where the master branch job is a pipeline the template is removed entirely.

Issue Number: N/A

Sandbox Testing

Test Links :

Are there any specific instructions or things that should be known prior to reviewing?

Other information

[lranjbar]

@MightyNerdEric For edgex-go there are some remaining snap jobs that would be in the view/project. We are still in the process of transitioning those jobs to pipelines. I could combine the yaml files for edgex-go this would make it more apparent.

[eb-oss]

Now the commit header is too long. :grimacing: Here's what I would suggest:

`Remove Fuji jobs in preparation for Geneva Release

This includes entirely removing the files for several projects that only had fuji streams.`

[lranjbar]

@MightyNerdEric Thanks for the commit message. :) I've updated and rebased