Remove pytorch_lightning.core.memory.get_gpu_memory_map

[puhuk]

To resolve issue #12521

What does this PR do?

Fixes #<issue_number>

Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

• Was this discussed/approved via a GitHub issue? (not for typos and docs)
• Did you read the contributor guideline, Pull Request section?
• Did you make sure your PR does only one thing, instead of bundling different changes together?
• Did you make sure to update the documentation with your changes? (if necessary)
• Did you write any new necessary tests? (not for typos and docs)
• Did you verify new and existing tests pass locally with your changes?
• Did you list all the breaking changes introduced by this pull request?
• Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

• Is this pull request ready for review? (if not, please submit in draft mode)
• Check that all items from Before submitting are resolved
• Make sure the title is self-explanatory and the description concisely explains the PR
• Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?

:)
Make sure you had fun coding 🙃

[rohitgr7]

I think for this we need to remove LoggerConnector.gpu_metrics, memory.get_memory_profile too since they are just sequential calls. Probably it can be done in separate PRs starting with gpu_metrics, then get_memory_profile, and finally get_gpu_memory_map.

[puhuk]

@rohitgr7 Ok, then let me take get_memory_profile as well from issue #12521.
But where can I find gpu_metrics, because there is no item in #12521

[rohitgr7]

@puhuk added at the end :)
you can do get_memory_profile and gpu_metrics together in a single PR if you want