Include a list of supported providers in OPTIONS /api/providers

[skateman]

@Hyperkid123 is working on the new API-driven forms for adding a provider and for that he needs a way to ask for the list of supported providers with their names and classes. Since ManageIQ/manageiq#18568 we can ask for the list of the provider classes that are available for adding via the UI.

$ curl -u admin:smartvm -XOPTIONS "http://localhost:3000/api/providers" | jq

{
 ...
  "data": {
    "provider_settings": {
       ...
    },
    "supported_providers": [
      {
        "title": "Ansible Tower Automation",
        "type": "ManageIQ::Providers::AnsibleTower::AutomationManager",
        "kind": "automation"
      },
      {
        "title": "Kubernetes",
        "type": "ManageIQ::Providers::Kubernetes::ContainerManager",
        "kind": "container"
      },
      {
        "title": "OpenShift",
        "type": "ManageIQ::Providers::Openshift::ContainerManager",
        "kind": "container"
      },
      {
        "title": "Lenovo XClarity",
        "type": "ManageIQ::Providers::Lenovo::PhysicalInfraManager",
        "kind": "physical_infra"
      },
      {
        "title": "Redfish",
        "type": "ManageIQ::Providers::Redfish::PhysicalInfraManager",
        "kind": "physical_infra"
      },
      {
        "title": "OpenStack Platform Director",
        "type": "ManageIQ::Providers::Openstack::InfraManager",
        "kind": "infra"
      },
      {
        "title": "Red Hat Virtualization",
        "type": "ManageIQ::Providers::Redhat::InfraManager",
        "kind": "infra"
      },
      {
        "title": "Microsoft System Center VMM",
        "type": "ManageIQ::Providers::Microsoft::InfraManager",
        "kind": "infra"
      },
      {
        "title": "VMware vCenter",
        "type": "ManageIQ::Providers::Vmware::InfraManager",
        "kind": "infra"
      },
      {
        "title": "Foreman Configuration",
        "type": "ManageIQ::Providers::Foreman::ConfigurationManager",
        "kind": "configuration"
      },
      {
        "title": "Amazon EC2",
        "type": "ManageIQ::Providers::Amazon::CloudManager",
        "kind": "cloud"
      },
      {
        "title": "Azure",
        "type": "ManageIQ::Providers::Azure::CloudManager",
        "kind": "cloud"
      },
      {
        "title": "Google Compute Engine",
        "type": "ManageIQ::Providers::Google::CloudManager",
        "kind": "cloud"
      },
      {
        "title": "OpenStack",
        "type": "ManageIQ::Providers::Openstack::CloudManager",
        "kind": "cloud"
      },
      {
        "title": "VMware vCloud",
        "type": "ManageIQ::Providers::Vmware::CloudManager",
        "kind": "cloud"
      }
    ]
  }
}

Originally I wanted to group these fields by the kind of the provider, but IMO this can be done on the client much easier. Maybe the kind and type keys should be changed to something else, I wasn't sure about the class as it might be a reserved word in other worlds.

@miq-bot add_reviewer @abellotti
@miq-bot add_reviewer @djberg96
cc @Hyperkid123, @agrare, @martinpovolny

[miq-bot]

Checked commit skateman@16845cd with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 🍰

[Fryguy]

Love it! Getting closer and closer to pure pluggability!

[Fryguy]

cc @agrare @gtanzillo

[agrare]

Love it @skateman !

[djberg96]

👍

[abellotti]

looks good, also adding the new element so not breaking compatibility, so 👍 from me.

[agrare]

🎉

[skateman]

@miq-bot add_label changelog/yes