Release 2.1.0

[philipliu]

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.
  paymentservice.stellar, 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.

What

This PR bumps the version numbers for the 2.1.0 release.

#953

Why

We are releasing 2.1.0

Known limitations

N/A

[stellar-jenkins]

Reference Server Preview is available here:
https://anchor-ref-pr951.previews.kube001.services.stellar-ops.com/
SEP Server Preview is available here:
https://anchor-sep-pr951.previews.kube001.services.stellar-ops.com/

[lijamie98]

Hey Philip,

Let's do these:

• Create an issue for Release 2.1.0 based on the issue templte.
• Refine the issue template if necessary
• Although the branch is in your forked repo, it would be nice if we follow the same branch naming as release/2.1.0.

[lijamie98]

Can you include this PR in release 2.1.0 because it was planeed in Jira.
#944

[lijamie98]

LGTM.

[stellar-jenkins]

Reference Server Preview is available here:
https://anchor-ref-pr951.previews.kube001.services.stellar-ops.com/
SEP Server Preview is available here:
https://anchor-sep-pr951.previews.kube001.services.stellar-ops.com/