Update changelog for 0.2 release

[urvisavla]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with name of package that is most changed in the PR, ex.
  services/friendbot, or all or doc if the changes are broad or impact many
  packages.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated any docs (developer docs, .md
  files, etc... affected by this change). Take a look in the docs folder for a given service,
  like this one.

Release planning

• I've reviewed the changes in this PR and if I consider them worthwhile for being mentioned on release notes then I have updated the relevant CHANGELOG.md within the component folder structure. For example, if I changed horizon, then I updated (services/horizon/CHANGELOG.md. I add a new line item describing the change and reference to this PR. If I don't update a CHANGELOG, I acknowledge this PR's change may not be mentioned in future release notes.
• I've decided if this PR requires a new major/minor version according to
  semver, or if it's mainly a patch change. The PR is targeted at the next
  release branch if it's not a patch change.

Update the changelog for the 0.2.0 release of go-stellar-sdk.

[Copilot]

Pull request overview

Updates the repository-level changelog to document the go-stellar-sdk 0.2.0 release, making the top-level release history reflect recent breaking changes, security fixes, and new features.

Changes:

• Added a top-level Pending section header.
• Added a new 0.2.0 section with categorized release notes (Breaking Changes, Security Fixes, New Features).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.