fix[auth]: Sanitize URL in cookie key to make it RFC 6265 compliant

[ahuseyn]

Tasks

• I have signed a Contributor License Agreement (CLA) with WP Engine.
• If a code change, I have written testing instructions that the whole team & outside contributors can understand.
• I have written and included a comprehensive changeset to properly document the changes I've made.

Description

This pull request focuses on improving RFC 6265 compliance for cookie keys in the @faustwp/core package by sanitizing the URL used in the cookie key. This ensures that the cookie key only contains valid characters, preventing potential issues with cookie handling in browsers.

Cookie key compliance improvements:

• Updated the construction of the tokenKey in the OAuth class (token.ts) to sanitize the URL, removing any characters not allowed by RFC 6265 section 4.1.1. This change helps prevent invalid cookie keys and improves compatibility across browsers.
• Added a changeset describing the patch for RFC compliance, referencing the related issue (Issue after cookie package update (0.5.0 → 0.7.0): authorization tokens no longer set due to stricter cookieNameRegExp #2181).

Related Issue(s):

• #2181

Testing

Tested manually with faustwp-getting-started example

Screenshots

Documentation Changes

Dependant PRs

[changeset-bot]

🦋 Changeset detected

Latest commit: 7026f8c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@faustwp/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌