fix(sagemaker): enhance idle activity monitoring for appropriate shutdown

[aws-ajangg]

Problem

• Users reported code editor and jupyterlab spaces were prematurely or not shutting down when connecting via remote ide. This issue has been addressed by enhancing the idle activity monitoring system

Solution

• Check for remote ide environment which triggers the last active timestamp script to update. previously this was skipped and the timestamp was not being updated which caused the space to not shut down when idle
• Add special case for focused window due to event handlers triggering for idle windows in the background
• Add remaining criteria for idle detection:

No background processes running
No notebook kernels processing
No unsaved work

• Check for active jupyterlab kernels

Test

• Tested idle detection locally with new VSIX
• Internal bugbash

---

• Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
• Your code changes must meet the guidelines in CONTRIBUTING.md.
• License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

• This pull request modifies code in src/* but no tests were added/updated.
  • Confirm whether tests should be added or ensure the PR description explains why tests are not required.
• This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
  • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
  • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

[sgganjo]

nit: can we rename api variable to something like jupyterExtApi or something to improve readability

[sgganjo]

what is executionSummary check ?

[aws-ajangg]

comment wasn't updated from an earlier impl of the fix. it's been addressed to update the current impl

[sgganjo]

Do we need to throw some kind of err/debug/logging info when we are not able to install the extension. Customer might not be sure what they need to do to allow extension installation specially if there is no internet access allowed in customer env.

[msgupta-amazon]

nit: To add a comment line instead of returning false when we don't find jupyterExt installed.

else Looks good to me.