Issue Summary

The API v1 for users doesn't accept the use of roleId 12 (team of teams) for Solution Teams, throwing the error "Role with id 12 is not valid for this team" if a POST is made to it (even if the user already has this roleId).
The problem is that the API v2 does accept the roleId 12 for Solution Teams, in fact, doing a PATCH to it without a roleId, it will assign this roleId

Steps to Reproduce

1. Add an user to a Solution Team through a PATCH using API v2 endpoint Users without providing the roleId
2. Now do a GET to this user on the API v1 endpoint Users
3. Use the same content and try a POST to the user, but now on API v1 and see the error

Expected Results

Both API v1 and v2 handle the roleId in the same way for different team types.

Actual Results

Each version handles the roleId different for Solution Team

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available