fix(core): decode encoded cookie name while creating universal storage

[HuiSF]

Description of changes

Issue #, if available

#11945

Description of how you validated changes

• Decode the cookie header before using the value to create a cookie store

Context

When Amplify.configure({ ssr: true }), the Cognito auth tokens will be stored in cookie store. This is handled by the package amazon-cognito-identity-js using js-cookie under the hood.

Per RFC 6265 section 4.1.1 and RFC 2616 section 2.2, a cookie name must be a token that doesn't contain any separators.

In the situation described in the linked issue, the cookie name contains '@' as a part of user email address, hence, js-cookie encodes it following above the aforementioned standard. However, the UniversalStorage creates a cookie store instance using the cookie header value directly, without decoding it, this further caused the issue.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jimblanc]

LGTM

[cwomack]

LGTM!