feat: Update Publish-* cmdlets to support json generation

[bhumitra]

In order to have a good experience with our community, we recommend that you read the contributing guidelines for making a pull request.

Summary of Pull Request
Updated Publish-* cmdlets to support json generation for -
Publish-BackupStatus
Publish-NsxtTransportNodeStatus
Publish-NsxtTier0BgpStatus
Publish-SnapshotStatus
Publish-LocalUserExpiry
Publish-StorageCapacityHealth

Added 2 new methods -
Publish-NsxtHealthNonSOS
Publish-ComponentConnectivityHealthNonSOS

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

#37
Issue Number: 37

Test and Documentation Coverage

• Tests have been completed (for bug fixes / features).
• Documentation has been added / updated (for bug fixes / features).

Breaking Changes?

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

New if/else path has been added to these cmdlets. if called using -jsonOutput, then json is generated. Else, the functionality is the same as before. I have tested the functionality and it works fine.

[vmwclabot]

@bhumitra, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit 970661d must be signed by [email protected]
• Commit 4055184 must be signed by [email protected]
• Commit 51855d3 must be signed by [email protected]
• Commit 6bafb4c must be signed by [email protected]
• Commit 787df2b must be signed by [email protected]

[tenthirtyam]

Closing in favor of #79.

[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.