Expose the verify_credentials action for /api/providers

[skateman]

Exposing the verify_credentials_task method as verify_credentials on /api/providers for the new provider forms. This action will return a task ID that can be polled for the credential verification of any provider. The request always requires a zone and the provider type, other provider-specific options are all optional.

Request:

# POST http://admin:smartvm@localhost:3000/api/providers
{
  "action": "verify_credentials",
  "resource": {
    "zone": {
      "id": 1
    },
    "type": "ManageIQ::Providers::Redhat::InfraManager"
  }
}

Response:

{
  "results": [
    {
      "success": true,
      "message": "Credentials sent for verification",
      "task_id": "366208",
      "task_href": "http://localhost:3000/api/tasks/366208"
    }
  ]
}

Related issue: ManageIQ/manageiq#18818

@miq-bot add_reviewer @abellotti
@miq-bot add_reviewer @lpichler
@miq-bot add_label ivanchuk/no, enhancement

cc @agrare @Fryguy @Hyperkid123

[miq-bot]

Checked commit skateman@5b61ddf with ruby 2.4.6, rubocop 0.69.0, haml-lint 0.20.0, and yamllint 1.10.0
1 file checked, 1 offense detected

app/controllers/api/providers_controller.rb

• ❗ - Line 122, Col 5 - Style/RescueStandardError - Avoid rescuing without specifying an error class.

[Fryguy]

Would like @agrare's approval before merge.

[skateman]

@Fryguy I'd like to wait for an opinion from @Hyperkid123

[Hyperkid123]

@skateman @Fryguy tried it in console and it works very well. I think we are very close to start doing some UI work too.

[abellotti]

@skateman can you add specs in a follow-up, thank you.

[skateman]

@abellotti sure, if you tell me what exactly should I test... 😕

[abellotti]

Maybe 3 specs, one with invalid role returning forbidden, one returning a successful "verify_credentials" action result and one returning a failed action (bad creds/ip/etc)
Thanks!!