ci(release): change to git from scratch approach

[elmariofredo]

to align it with https://github.com/atlassian/lerna-semantic-release example and hopefully prevent issues with detached tags

Closes #222

Please check if the PR fulfills these requirements

• [x] The commit message follows our guidelines: https://github.com/wc-catalogue/blaze-elements/blob/master/docs/CONTRIBUTING.md#commit
• [x] There are no linting errors and code is properly formatted (your run before push yarn ts:format && yarn ts:lint:fix)
• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Other... Please describe:

What is the current behavior? (You can also link to an open issue here)

What is the new behavior?

Does this PR introduce a breaking change? (check one with "x")

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[elmariofredo]

For unknown reason they are wiping whole git see https://github.com/atlassian/lerna-semantic-release/issues/72#issuecomment-286028831

[elmariofredo]

Closing in favour of #312