chore(build): build and push images from libcstor

[mittachaitu]

Signed-off-by: mittachaitu sai.chaithanya@mayadata.io

Pull Request template

Please, go through these steps before you submit a PR. ## Remove this line

Why is this PR required? What issue does it fix?: This PR is required to fix the licensing issue in cStor repo.

What this PR does?: This PR does the following changes:

• Moves the zrepl.c from cstor/cmd/zrepl to libcstor/cmd/zrepl.
• Adds the required auto makefiles to compile and generate zrepl binary.
• Moves the build process(amd64 and arm) from cstor repo to libcstor repo.
• Updates the downstream repo from openebs/cstor to openebs/istgt.
• Update RELEASE.md and developer-setup.md with relevant changes.

NOTE:

• Following is the dependency reslese openebs/cstor -> openebs/libcstor -> openebs/istgt.

Does this PR require any upgrade changes?: No

If the changes in this PR are manually verified, list down the scenarios covered and commands you used for testing with logs:

• Ran the test locally.
• Verified by compiling and executing standalone binaries.
• Built an image and used that image to provision cStor pools in the K8s environment.
• Ran the Travis in local repo(check status here).

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:

[mittachaitu]

few licesne files are saying 2017-2019, can we update them.

Actually they were written and last updated during that time frame so kept them as is... Should I need to update them to 2020/2018-2020?

[pawanpraka1]

Actually they were written and last updated during that time frame so kept them as is... Should I need to update them to 2020/2018-2020?

as they are new file to this repo, we can add 2020 in the copyright.

[mittachaitu]

Actually they were written and last updated during that time frame so kept them as is... Should I need to update them to 2020/2018-2020?

as they are new file to this repo, we can add 2020 in the copyright.

Done

[mittachaitu]

these changes need the .md file changes as well in both the repos.

@vishnuitta updated the RELEASE.md and developer-setup.md files with new changes