modifying SyncBN doc for FP16 use case

[mseth10]

Description

Updating docs to add instructions for MXNet users on SyncBN FP16 support and possible workarounds. This fixes #13976 .

Checklist

Essentials

Please feel free to remove inapplicable items for your PR.

• The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
• Changes are complete (i.e. I finished coding on this PR)
• All changes have test coverage:
• Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
• Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
• Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
• Code is well-documented:
• For user-facing API changes, API doc string has been updated.
• For new C++ functions in header files, their functionalities and arguments are documented.
• For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
• Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
• To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

• SyncBN doc

Comments

• If this change is a backward incompatible change, why must this change be made.
• Interesting edge cases to note here

[vandanavk]

@mxnet-label-bot add [pr-awaiting-review, Doc]

[vandanavk]

@mxnet-label-bot update [pr-awaiting-merge, Doc]

@aaronmarkham for review/merge

[lupesko]

So does it not support training or inference?
You say training in this line, and refer to inference in the next line.

[mseth10]

SyncBN does not have FP16 support for both training and inference. But for FP16 inference, SyncBN can be replaced with nn.BatchNorm as they have similar functionality.