[ DEVOI-638 ] Changes for publish step to add env and app in upload path

[ayush-lr]

Context

In parallel pubishing support, when running command

 Uploading build/kubernetes/master/build/28077/<env>/<app_name>/manifests_local-staging_stable.yaml to gs://com-eng-ops-hub-services-spinnaker-pipeline/kubernetes/project/LiveRamp/<repo_name>/master/build/28077/artifact/manifests_local-staging_stable.yaml

Even if we made the path build/kubernetes/master/build/28077/<env>/<app_name>/manifests_local-staging_stable.yaml unique, the GCS path is not unique:

gs://com-eng-ops-hub-services-spinnaker-pipeline/kubernetes/project/LiveRamp/<repo_name>/master/build/28077/artifact/manifests_local-staging_stable.yaml

So, while one manifest got published right now, another step could use/move the manifest of another app another gstuil mv or cp cmd execution.

Description

Ticket: https://liveramp.atlassian.net/browse/DEVOI-638

Work Done

So, added a new publish method with optional seperate cmd line options calling a new upload method internally.

[ranesagar]

Hey @ayush-lr - The env arg is already supported in KDT so I am not sure if it is needed. Let's schedule some time later this week to go over the changes.

[ayush-lr]

Will book a slot in your calendar

[ayush-lr]

The word env is just an example of command line parameter. Will not clash with any usage of env as a keyword.