fix(clerk-js): Avoid depending on count as it can be zero but invitations may still exist

[panteliselef]

Description

Background: In order to provide a better UX, we are manually updating the cache where userInvitations are stored. This allows us to update the invitation in place and avoid layout shifts, if we would simply revalidate this would not be possible.

We are also manually updating count in the local cache in order to display the correct number of invitations available, without revalidating as this would cause a layout shift.

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:

[changeset-bot]

🦋 Changeset detected

Latest commit: d0f8df5

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

[octoper]

!preview

[dimkl]

❓ what is the actual use case where we want to have count 0 with invitations?
If there is no case (product wise) i think we need to open a bug ticket to the backend team to fix this.

[clerk-cookie]

Hey @octoper, your preview is available.

Status	Preview	Updated (UTC)
🍪 Deployed	Visit preview	Apr 02, 2024 01:39 PM

[panteliselef]

❓ what is the actual use case where we want to have count 0 with invitations? If there is no case (product wise) i think we need to open a bug ticket to the backend team to fix this.

@dimkl I updated the description. Generally count is very useful, for this particular case and because we manually update the cache instead of revalidating we need to use this differently.

[octoper]

💯

[dimkl]

@panteliselef Is the userInvitations or userSuggestions paginated responses? If so, is the count related to the total count data of the response?
If the count is related to the total count of the paginated response, i think we still need to depend on that instead of the length. Wdyt?