Define JS-Dataverse CHANGELOG strategy

[g-saracca]

Overview of the Feature Request
We currently do not have a CHANGELOG for the Dataverse Client Javascript repository. We should define a process to create and maintain one, so that all changes are clearly documented and easy to review.

What kind of user is the feature intended for?
Community

What inspired the request?
Sprint planning discussion

What existing behavior do you want changed?
N/A
Any brand-new behavior do you want to add to Dataverse?
N/A
Any open or closed issues related to this feature request?
None

[jggautier]

How would this be related to the "Changes from the original Dataverse JSF application" section of the Readme of the dataverse-frontend repo?

[g-saracca]

Hey @jggautier , this is more for tracking what has changed/added/fixed from one release to another.