Userschema for registration vs. userschema for user profile

[erral]

Our current @userschema endpoint returns the full user schema as defined in Plone.

But in Plone we have different user schemas, one for the registration form and the other one for the user profile form.

They are, in essence, the same user profile, but filtered according to the field settings, where one can set whether a given field will be shown in the registration form, in the user profile form, in both, or in neither of them.

So I propose that we add a parameter to the @userschema endpoint, so that only user registration fields or only user profile fields can be requested.

@ionlizarazu

[erral]

This can be relevant for plone/volto#6435

[erral]

Or we can create a different endpoint @registration-userschema that returns the fiels available for registration.

[davisagli]

@erral It makes sense that we need a separate way to get the userschema for registration. Can we make the endpoint @userschema/registration instead of @registration-userschema? It just keeps it organized a bit better, I think, and we can document both userschema endpoints together.

[erral]

Yep, nice idea