DXCDT-264: Add api command

[sergiught]

🔧 Changes

With this PR we are introducing a brand new command: auth0 api. This enables making an authenticated arbitrary HTTP request to the Auth0 Management API.

One of the reasons we're introducing this right now is to be able to quickly fill the gaps that the CLI has in terms of managing certain resources.

$ auth0 help api
Makes an authenticated HTTP request to the Auth0 Management API and prints the response as JSON.

The method argument is optional, and when you don’t specify it, the command defaults to GET for requests without data
and POST for requests with data.

Auth0 Management API Docs:
  https://auth0.com/docs/api/management/v2

Available Methods:
  GET, POST, PUT, PATCH, DELETE

Usage:
  auth0 api <method> <uri> [flags]

Examples:
auth0 api "/organizations?include_totals=true"
auth0 api get "/organizations?include_totals=true"
auth0 api clients --data "{\"name\":\"apiTest\"}"


Flags:
  -d, --data string   JSON data payload to send with the request.
  -h, --help          help for api

Global Flags:
      --debug           Enable debug mode.
      --force           Skip confirmation.
      --format string   Command output format. Options: json.
      --no-color        Disable colors.
      --no-input        Disable interactivity.
      --tenant string   Specific tenant to use.

Screen.Recording.2022-11-28.at.13.51.38.mov

📚 References

• Provide way to make arbitrary api calls #479

🔬 Testing

📝 Checklist

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

[willvedd]

Great first pass! Much of the design is sensible. Lots of little changes requested but nothing that would require a large refactor.

[willvedd]

Similarly to other feedback, this error could be more human friendly. I think we'd have a good idea of when and how this error triggers, so we could provide clearer guidance on how to correct.

See: https://clig.dev/#errors

[sergiught]

The returned error wraps all inner errors so the final one ends up to be for example:

$auth0 api put z --data {"zz:2} 
"

=== tenat-example.auth0.com error

 ▸    failed to parse command inputs: invalid json data given: {zz:2}

exit status 1

What do you suggest so we make it more human friendly? As in this case it's particularly hard as the json.Valid just returns true or false and isn't able to tell that the input was missing a ".