chore: handle error when saving push notification token

[gkartalis]

This PR resolves []

Description

@dariakoko noticed this issue bubbling up in sentry and we decided to add a try catch block and an info level captureMessage to prevent bubbling the error this way and have a less scary error message.

PR Checklist

• [ ] I have tested my changes on iOS and Android.
• [x] I hid my changes behind a feature flag, or they don't need one.
• [x] I have included screenshots or videos, or I have not changed the UI.
• [x] I have added tests, or my changes don't require any.
• [x] I added an app state migration, or my changes do not require one.
• [x] I have documented any follow-up work that this PR will require, or it does not require any.
• [x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

• [ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates

### Changelog updates #### Cross-platform user-facing changes - #### iOS user-facing changes - #### Android user-facing changes - #### Dev changes - handle error when saving push notification token - darianorge

Need help with something? Have a look at our docs, or get in touch with us.

[ArtsyOpenSource]

This PR contains the following changes:

• Dev changes (handle error when saving push notification token - darianorge)

  Generated by :no_entry_sign: dangerJS against f7187936a74ac86894160ec326f4a92626909a28

[damassi]

Yah, I agree with @araujobarret - Send this out via codepush, get some more intel!