docs: Create changelog guidelines (Closes #461)

[prapulkrishna-shaik]

Description:

Related issue(s):

Fixes #

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[prapulkrishna-shaik]

Description:
Creates a new changelog guidelines document in docs/sdk_developers/ and links to it from the CONTRIBUTING.md file.

Related issue(s):
Closes #461

[exploreriii]

Hi @prapulkrishna-shaik
Unfortunately, I cannot see any change to your changelog.md file, it is blank, did you intend to add content to it?

i realise I was not clear in the issue
To close the issue, changelog.md should explain to users the following:

It should link the issue solved by their pull request

Clear language but descriptive language. For example, try to avoid eg "refactored token create", instead say eg "refactored keys in token_create to avoid harcoding"

1-2 sentences.

Add their entry to the top of the file, under unreleased.

Explain to them what the unreelased sections mean, like fixed, added and changed and how to decide where theirs best fits.

We should provide good examples of changelog entries.

[exploreriii]

hi @prapulkrishna-shaik is still ongoing? This is a really important issue that we need resolved

[exploreriii]

Hi @prapulkrishna-shaik I am closing this PR and re-assigning as it seems it is no longer being worked on after asking twice.
Please do feel free to have a go at any other issue!
Thank you so much and apologies for the inconvenience