fix: use users-permissions as non-plugin collections

[nclsndr]

What does it do?

Solution Implemented

Added auto-detection for well-known Strapi resources like users:

Key Changes:

1. src/client.ts

   • Added WELL_KNOWN_STRAPI_RESOURCES mapping that identifies special content-types
   • Modified collection() method to auto-apply plugin configuration for 'users'
   • Preserved backward compatibility (explicit plugin options override auto-detection)

2. tests/unit/client.test.ts

   • Added test for auto-detection of 'users' resource
   • Added test for explicit plugin override

3. tests/unit/content-types/collection/collection-manager.test.ts

   • Added test verifying data wrapping behavior for regular vs special content-types

4. README.md

   • Added documentation section explaining users-permissions auto-detection

Usage

Before (required manual configuration):

const users = client.collection('users', {
  plugin: { name: 'users-permissions', prefix: '' }
});

After (works automatically):

const users = client.collection('users');
await users.create({
  username: 'john',
  email: 'john@example.com',
  password: 'SecurePass123!'
});

How to test it?

const users = client.collection('users');
await users.create({
  username: 'john',
  email: 'john@example.com',
  password: 'SecurePass123!'
});

Related issue(s)/PR(s)

Fixes #90

[Convly]

Could you also update https://github.com/strapi/client/blob/main/CONTRIBUTING.md#-testing-the-changes ?

[Convly]

Could you also update main/CONTRIBUTING.md#-testing-the-changes ?

🤦 I meant this review to be for #105 but you've already modified the file over there, feel free to ignore this one

[innerdvations]

Very nice, lgtm! Tested and works for me.

I don't see any issues aside from the question about single types, which I think can be resolved later, unless you want to address it here.

[Convly]

LGTM with the upcoming PR for single types.

As a quick note, I'm a bit concerned about the addition of all those edge cases (first for prefixes, then hard-coded stuff for plugins & U&P, and now WELL_KNOWN_STRAPI_RESOURCES). But hopefully this is the last hard coded edge case we'll have to deal with thanks to the upcoming generated API which should eliminate the need for these 🙏

[innerdvations]

edge cases

The thing is, these are kind of like edge cases in Strapi CMS and are the exact sort of thing the client should work around, to make it transparent to the user and easier to work with.

But yes, almost every workaround we build into strapi/client is something that in Strapi v6 we should probably make a breaking change to align with the standard way of doing things.