chore(clerk-js): Apply deprecation warnings

[dimkl]

Description

Review it per commit

Deprecation warnings added in @clerk/clerk-js:

• Organization.create() using string parameter
• Organization.retrieve() limit & offset
• Clerk.getOrganizationMemberships()
• svgUrl
• avatarUrl/logoUrl/faviconUrl/profileImageUrl

Notes: We cannot show deprecation warnings in console for deprecated type properties (eg UserJSON.profile_image_url)

TODO:

• support deprecation warnings for nested props in separate PR

Relevant PRs:

• Deprecate clerk set session #1800

Checklist

• npm test runs as expected.
• npm run build runs as expected.
• (If applicable) JSDoc comments have been added or updated for any package exports
• (If applicable) Documentation has been updated

Type of change

• 🐛 Bug fix
• 🌟 New feature
• 🔨 Breaking change
• 📖 Refactoring / dependency upgrade / documentation
• other:

Packages affected

• @clerk/clerk-js
• @clerk/clerk-react
• @clerk/nextjs
• @clerk/remix
• @clerk/types
• @clerk/themes
• @clerk/localizations
• @clerk/clerk-expo
• @clerk/backend
• @clerk/clerk-sdk-node
• @clerk/shared
• @clerk/fastify
• @clerk/chrome-extension
• gatsby-plugin-clerk
• build/tooling/chore

[changeset-bot]

🦋 Changeset detected

Latest commit: af4b7ba

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

This PR includes changesets to release 3 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/chrome-extension	Patch
@clerk/clerk-expo	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

[dimkl]

@nikosdouvlis PTAL

The logoUrl properties from the snapshots even though they still exist in those classes because of the way the deprecation helper works to mark the property as deprecated.
The deprecation helper redefine the property in the class prototype using a getter/setter that shows a warning in getter using the Object.defineProperty(). By redefining a property, that property is not considered class own property any more which causes the jest snapshot and the JSON.stringify() to omit that property.
This is a side-effect of the deprecation implementation and not a spec but i think that we are okay to proceed with omitting the properties from snapshots.

ref: 4dde358

[panteliselef]

@dimkl could we skip deprecating nested properties for this PR and resolve it in a followup ?

[clerk-cookie]

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.