[SDK-3642] feat: support complex field names in export_users

[stevehobbsdev]

Changes

This PR tweaks export_users so that it could now accept (and properly forward) field names and export_as settings to the jobs/users-exports endpoint. Previously it was only possible to specify an array of field strings. Now, objects can be specified meaning that the export_as property can be specified.

This is done in a backwards-compatible way so as not to break those still sending string arrays.

Usage example:

auth0.export_users(
  fields: [{ name: 'author', export_as: 'creator' }],
  connection_id: 'test-connection',
  format: 'csv',
  limit: 10
)

References

Fixes #378

Testing

Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

• This change adds unit test coverage
• This change adds integration test coverage
• This change has been tested on the latest version of Ruby

Checklist

• I have read the Auth0 general contribution guidelines
• I have read the Auth0 Code of Conduct
• All existing and new tests complete without errors
• Rubocop passes on all added/modified files
• All active GitHub checks have passed