feat(template): Automatically define release

[ruslan-kurchenko]

1. Automatically define release file on successful build

[ruslan-kurchenko]

@azlam-abdulsalam based on your comment:

We are planning to classify environments into DEV, TEST and RELEASE
DEV will be your scrathorg/sandbox used for development.  Sandbox/Scratch Org pools also falls into the category
TEST will be a collection of environments, all parallel as opposed to a pipeline ( say ST || SIT || Performance) and you test on any of the environments depending on the risks associated with the change
RELEASE will be environment such as staging and production
So a pipeline is basically DEV -- TEST -- RELEASE , and as always each stage is async.
Note, I am planning to completely remove any reference to UAT or AT from an environment perspective and will be  recommend to do it in any of the stages.

1. Should we consider changing the "Deploy to DEV" step to a different name?
2. How are changes look like from your perspective?

[crazynammer]

Update the new line "35" for the reference to "azure pipelines" as this is a github workflow.

The sample pipelines utilize an azure pipelines

[crazynammer]

Looks good otherwise. Let's do the quick fix, merge, and I'll test it end to end on my personal github and we can find any bugs as needed.