Usercube connector documentation updated

[nliATusercube]

Usercube is now part of Netwrix and our product offical name is: "Netwrix Usercube"

[prmerger-automator]

@nliATusercube : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 73be943:

✅ Validation status: passed

File	Status	Preview URL	Details
powerquery-docs/connectors/index.md	✅Succeeded
powerquery-docs/connectors/media/usercube/usercube-client-credentials.png	✅Succeeded
powerquery-docs/connectors/media/usercube/usercube-get-data.png	✅Succeeded
powerquery-docs/connectors/media/usercube/usercube-import-data-navigator.png	✅Succeeded
powerquery-docs/connectors/media/usercube/usercube-server.png	✅Succeeded
powerquery-docs/connectors/usercube.md	✅Succeeded
powerquery-docs/toc.yml	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prmerger-automator]

PRMerger Results

Issue	Description
Yaml File(s)	This PR includes changes to .yml file(s) owned by another author.
File Change Percent	This PR contains file(s) with more than 30% file change.
Image File	This PR added or updated an image file(s).
Index File	This PR contains a change to the index file.

[American-Dipper]

@bezhan-msft - can you review the proposed changes?

IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"

@MicrosoftDocs/public-repo-pr-review-team

[ptyx507x]

@nliATusercube please work through the certification portal to submit a new version of your connector that contains those changes. Once those changes are certified, they can be reflected in the public documentation for the connector.

[JasonWHowell]

#reassign:ptyx507x

[ktoliver]

The content has been moved or reconfigured since the pull request was opened. The pull request can't be merged in, so we'll need to close it. If the proposed update still needs to be added to the article, please submit it in a new pull request. Thanks.