Added support for root attributes when creating a new user

[cocojoe]

Added support for root attributes when creating a new user
Added Tests
Also fixed a warning in state string generation

Changes

Public API Change to createUser which now accepts an optional rootAttributes parameter.

     - parameter email:             email of the user to create
     - parameter username:          username of the user if the connection requires username. By default is 'nil'
     - parameter password:          password for the new user
     - parameter connection:        name where the user will be created (Database connection)
     - parameter userMetadata:      additional userMetadata parameters that will be added to the newly created user.
     - parameter rootAttributes:    root attributes that will be added to the newly created user. See https://auth0.com/docs/api/authentication#signup for supported attributes. Will not overwrite existing parameters.
     
     - returns: request that will yield a created database user (just email, username and email verified flag)
func createUser(email: String, username: String?, password: String, connection: String, userMetadata: [String: Any]?, rootAttributes: [String: Any]?)

References

https://auth0.com/docs/api/authentication#signup

Testing

Manually tested as well.

• This change adds unit test coverage
• This change has been tested on the latest version of the platform/language or why not

Checklist

• I have read the Auth0 general contribution guidelines
• All existing and new tests complete without errors
• All active GitHub checks have passed

[lbalmaceda]

what about the method signUp on the Authentication classes, shouldn't it also expose this functionality?

[lbalmaceda]

this behavior should be clarified in the method documentation

[cocojoe]

That seems fair, it was intended to stop abuse like overwriting of core params

[lbalmaceda]

That's no abuse IMHO. The user should be free to send whatever they want as "additional params". If they send something we already specify, that's their fault.

[cocojoe]

I agree with you in principal.

[lbalmaceda]

protocols' methods can be changed without breaking users? this is a public one.

[stevehobbsdev]

This looks like an optional argument, and it's placed at the end of the parameter list so I'm not sure it would be a breaking change.

[cocojoe]

The argument is optional so in use you don't need to specify it. However, Lucho is correct any class that implements the protocol still has to support the behaviour. As the Protocol is Public then we should try to avoid breaking it.

I'll add support for this in the Public Extension so the original method will still work out of the box as the method in the Public Extension is a fallback.

[cocojoe]

what about the method signUp on the Authentication classes, shouldn't it also expose this functionality?

It's a deprecated endpoint (non-oidc)