Updates CHANGELOG to match base.store's March Release Notes

[danzanzini]

What's the purpose of this pull request?

This PR updates the CHANGELOG so it matches it's March Release Notes.
I've also added the identifier of the PR to each CHANGELOG entry so we don't need to rely on git blame to identify the PR responsible for the entry.

How does it work?

Each entry that was merged before #392 was added to the 0.2.0 section. A new Github release was also added to reflect this state.

Each entry after this is still in the Unreleased section.

How to test it?

Check if the CHANGELOG makes sense and doesn't have any wrong information.

References

https://keepachangelog.com/en/1.0.0/

Checklist

You may erase this after checking them all ;)

• CHANGELOG entry added

[vtex-sites]

Preview is ready

This pull request generated a Preview

👀   Preview: https://preview-450--base.preview.vtex.app
🔬   Go deeper by inspecting the Build Logs
📝   based on commit b604396

[gatsby-cloud]

Gatsby Cloud Build Report

basestore

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 8m

Performance

Lighthouse report

Metric	Score
Performance	💚 97
Accessibility	💚 100
Best Practices	💚 93
SEO	💚 93

🔗 View full report

[mariana-caetano]

Awesome @danzanzini! 🎉 Just one thing to add is that the PRs from February were mentioned in the Full Changelog section of the Release Notes (at the beginning of it) since the main focus was the March PRs. Either way LGTM.

[danzanzini]

@mariana-caetano Do you think it's worth creating a section below the 0.2.0 for entries from February?

[mariana-caetano]

@mariana-caetano Do you think it's worth creating a section below the 0.2.0 for entries from February?

@danzanzini It sounds like a good idea, but do you mean also creating a 0.1.2 release to it?

[danzanzini]

A proper release is not necessary but I can create a tag to reflect the state of the code