Infer dtype in SymbolBlock import from input symbol (v1.3.x)

[lebeg]

Description

A port of #12412 to 1.3.x branch.

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

• Feature1, tests, (and when applicable, API doc)
• Feature2, tests, (and when applicable, API doc)

Comments

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

[lebeg]

@sandeep-krishnamurthy

[lebeg]

@nswamy

[szha]

A likely easier way to add the changes is to provide a list of commits that committers can cherry-pick. The branch CI will still be triggered after picking.

[lebeg]

@szha I'm making sure that there are no conflicts by rebasing the changes to the branch. What has been added (for a changelog, for example) would be easier to track and review as well.

[anirudhacharya]

@mxnet-label-bot [pr-awaiting-merge]