[BUG]: In volume details, io_limit_policy dictionary in key 'name' is holding 'id' value.

[Piaskun]

Describe the bug
If volume has io_limit_policy applied, on volume details we have:

"io_limit_policy": {
  "id": "qp_2",
  "name": "qp_2"
},

So for both 'id' and 'name' key, dictionary has 'id' value.

To Reproduce
Steps to reproduce the behavior:

1. Set IO policy on volume
2. Query volume details
3. io_limit_policy dictionary has io_policy id in both 'id' and 'name' keys.

Expected behavior
io_limit_policy dictionary has io_policy name value under 'name' key.

Additional context
I suspect bug in:
volume.py line 971:

            if obj_vol.io_limit_policy:
                volume_details.update(
                    {'io_limit_policy': {'name': obj_vol.io_limit_policy.id,
                                         'id': obj_vol.io_limit_policy.id}})

[Piaskun]

I can confirm, that change in volume.py line 971

            if obj_vol.io_limit_policy:
                volume_details.update(
                    {'io_limit_policy': {'name': obj_vol.io_limit_policy.name,
                                         'id': obj_vol.io_limit_policy.id}})

fixed this issue

[anupamaloke]

Hi @Piaskun, thank you for reporting this issue and the fix. Would you also like to submit a PR may be :-)