Add getting Manila from the service catalogue

Overview

Related to #445 (closed), the service catalogue returns token information which includes a Service Catalogue. There is an entry for Manila which looks something like the following:

      {
        "endpoints": [
          {
            "id": "27486d07473e46ef918d66a96943d282",
            "interface": "internal",
            "region": "IU",
            "region_id": "IU",
            "url": "https://js2.jetstream-cloud.org:8786/v1/95e98332bb62488eba5fee7c5849e13c"
          },
          {
            "id": "3f2a14de9d1145a2858031821b1e51bc",
            "interface": "admin",
            "region": "IU",
            "region_id": "IU",
            "url": "https://js2.jetstream-cloud.org:8786/v1/95e98332bb62488eba5fee7c5849e13c"
          },
          {
            "id": "5e718bb7806f4de6a9c35b1d97a2c7ba",
            "interface": "public",
            "region": "IU",
            "region_id": "IU",
            "url": "https://js2.jetstream-cloud.org:8786/v1/95e98332bb62488eba5fee7c5849e13c"
          }
        ],
        "id": "95d79f12f44e4faa91c4ca5a3b157960",
        "name": "manila",
        "type": "share"
      },

This change makes sure that Exosphere parses that into its own ServiceCatalog.

How to Test

• When adding an OpenStack project, there should be no visible errors (if the project has a Manilla endpoint).

Screenshots

N/A