Proper support for Remote Stop and Remote Abort with NeptuneLogger

[Raalsky]

What does this PR do?

With Remote Stop and Remote Abort in Neptune UI you're able to stop currently running training this means:

• Neptune will stop the current Run and wait to sync all the remaining operations to the server
• Once it's synced it's going to send a signal to kill current process

As we're doing a stop operation before sending the signal to Lightning the Run may be in an inactivate state when reaching the logger finalization code raising a related exception. This PR prevents this behavior and allows to make graceful shutdown.

Fixes neptune-ai/neptune-client#1378

Before submitting

• Was this discussed/agreed 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 minor internal changes/refactors)

PR review

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

Reviewer checklist

• 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

---

📚 Documentation preview 📚 : https://pytorch-lightning--19130.org.readthedocs.build/en/19130/

[codecov]

Codecov Report

Merging #19130 (102a0e3) into master (a41528c) will decrease coverage by 34%.
The diff coverage is 100%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #19130      +/-   ##
==========================================
- Coverage      82%      48%     -34%     
==========================================
  Files         450      442       -8     
  Lines       38253    38111     -142     
==========================================
- Hits        31454    18442   -13012     
- Misses       6799    19669   +12870     

[Borda]

let's update or rebase after #19265 lands 🎏

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sub></sup>

[Raalsky]

@Borda Ready for review 😉

[szysad]

LGTM!