ci: enable new ci and build.yml changes

[dsharma-dc]

Pull Request template

Please, go through these steps before you submit a PR.

Why is this PR required? What issue does it fix?:

What this PR does?:

Does this PR require any upgrade changes?:

If the changes in this PR are manually verified, list down the scenarios covered::

Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Fixes #
• PR Title follows the convention of <type>(<scope>): <subject>
• Has the change log section been updated?
• Commit has unit tests
• Commit has integration tests
• (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
• (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

[tiagolobocastro]

How is tagged release handled?

[dsharma-dc]

How is tagged release handled?

That's in #340 if that's what you are asking.

[dsharma-dc]

@Abhinandan-Purkait I see a very strange thing, that the output of below command that we have in workflow files varies between zfs vs lvm repos.

awk -F': ' '/^version:/ {print $$2}' deploy/helm/charts/Chart.yaml

In zfs, it correctly returns e.g. 2.7.0-develop. In lvm it is returning the first field i.e. the string version ! I don't see any difference in Chart.yaml formattting. Using single $ in print works correctly. I will change this to use single $ as I think it's just a typo that there are two $$ inadvertently.