Corrrectly display multiple upstream URIs

[velimir]

Proposed Changes

This pull request makes federation page correctly display upstreams with multiple URIs configured:

Federations accepts multiplie URIs to configure upstreams:

single upstream

{
  "component": "federation-upstream",
  "vhost": "/",
  "name": "single-upstream",
  "value": {
    "uri": "amqp://guest:guest@rabbit2",
    "ack-mode": "on-confirm",
    "trust-user-id": false
  }
}

multiple upstreams

{
  "component": "federation-upstream",
  "vhost": "/",
  "name": "multi-upstreams",
  "value": {
    "uri": [
      "amqp://guest:guest@rabbit2",
      "amqp://guest:guest@rabbit3"
    ],
    "ack-mode": "on-confirm",
    "trust-user-id": false
  }
}

which results in the following response:

[{
    "value": {
        "ack-mode": "on-confirm",
        "trust-user-id": false,
        "uri": ["amqp://guest:guest@rabbit2", "amqp://guest:guest@rabbit3"]
    },
    "vhost": "/",
    "component": "federation-upstream",
    "name": "multi-upstreams"
}, {
    "value": {
        "ack-mode": "on-confirm",
        "trust-user-id": false,
        "uri": "amqp://guest:guest@rabbit2"
    },
    "vhost": "/",
    "component": "federation-upstream",
    "name": "single-upstream"
}]

Before the change

After the change

Types of Changes

What types of changes does your code introduce to this project?

• Bugfix (non-breaking change which fixes Definition display isssue for dynamic shovels rabbitmq-shovel-management#21)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (correction or otherwise)
• Cosmetics (whitespace, appearance)

Checklist

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in related repositories

[michaelklishin]

Thank you!

[lukebakken]

Thank you. I reproduced this using master and confirmed this fix with the patch applied 👍

[lukebakken]

Backported to v3.7.x