Patch swagger.json to represent '/v1/personalities' correctly

[spacegospod]

Summary of Pull Request

The swagger.json file has an incorrect entry for the "/v1/personalities" endpoint.
The service returns a page object and the actual payload is under a key called "elements". This is a common pattern across the VCF APIs. In our version of the API spec however the endpoint response is listed as an array which result in a failure to unmarshal the response body when attempting to use the bindings.

I am patching the bindings so that they match the implementation.
Verified that this solution works by calling the API via the bindings on a live environment

Type of Pull Request

• This is a bug fix.
• This is an enhancement or feature.
• This is a code style/formatting update.
• This is a documentation update.
• This is a refactoring update.
• This is a chore update
• This is something else.
  Please describe:

Related to Existing Issues

Issue Number: N/A

Test and Documentation Coverage

For bug fixes or features:

• Tests have been completed.
• Documentation has been added/updated.

Breaking Changes?

• Yes, there are breaking changes.
• No, there are no breaking changes.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.