Plugin specific support (users-permissions)

[jhoward1994]

What does it do?

Adds plugin-specific handling to the Strapi client library. The changes include:

• Added optional plugin configuration parameter to ContentTypeManagerOptions with configurable name and prefix
• Implemented conditional data wrapping logic that skips wrapping payloads for the users-permissions plugin
• Enhanced route construction to support plugin-specific prefixes (e.g., /plugin-name/resource or /resource for plugins without prefixes)
• Updated the client's collection() method to accept plugin configuration options

Why is it needed?

The users-permissions plugin in Strapi has a different API contract than regular content-types. It expects raw payload data without the standard { data: {...} } wrapper that other content-types require. Without this change, attempting to create users via the client fails with validation errors because the API receives the data in an unexpected format.

How to test it?

1. Set up a Strapi application with users-permissions plugin enabled
2. Use the client to create a user with plugin configuration:

   const users = client.collection('users', { 
     plugin: { name: 'users-permissions', prefix: '' } 
   });
   
   await users.create({
     username: 'testuser',
     email: '[email protected]',
     password: 'password123',
     role: 1
   });

3. Verify the request succeeds and the user is created
4. Run the test suite to verify all plugin-specific behaviors work correctly

Related issue(s)/PR(s)

[innerdvations]

shouldn't prefix be undefined here (and the test above this) to make sure it doesn't prefix that specific plugin? or am I misunderstanding it?

[innerdvations]

LGTM!

Still not 100% happy with needing the prefix but that's u&p's fault and we can work on improving it later