Refactor and migrate cf-deployment pipeline to upstream repo

[bikramnehra]

Is your feature request related to a problem? Please describe. Parent Issue: https://github.com/SUSE/kubecf/issues/220

This task requires following pipelines to be moved to upstream repo:

• cf-deployment

Describe the solution you'd like The plan is to keep the pipelines compatible while addressing following items in upstream repo:

• Make required changes in deployment script for it to deploy updated pipelines.
• Redundancy while building release images must be addressed.
• Ability to build multiple release versions using a simple yaml structure needs to be implemented.

Additional context This task is subject to following items:

• Gain access to IBM infrastructure(using lastpass) to deploy and test pipelines.
• Make all the required secrets available for the pipelines to be deployed.
• Make sure concourse versions are compatible.

[bikramnehra]

Based on feedback from @troytop we might have to re-scope this task to keep the two pipelines separate while figuring out a mechanism to share the pipeline codebase.

[bikramnehra]

Based on recent developments, the home for suse-buildpacks pipeline should be:https://github.com/cloudfoundry-incubator/kubecf/tree/master/.concourse

[bikramnehra]

As per @viovanov we can rename the cf-operator-ci repo to kubecf-ci and make that home for all release image related pipelines.

[fargozhu]

@bikramnehra we have an internal story related to buildpacks pipeline for the coming sprint so I do not know the impact that moving them will have. Let me sync with @thardeck about it.

[bikramnehra]

As discussed, broken the task in two chunks - other task is: https://github.com/cloudfoundry-incubator/kubecf/issues/601