when following logs (kubectl logs -f), a ctrl+c should be handled by plugin to release tail to save resource

[antoinetran]

Short Description of the issue

With the implementation of #35 , the logs are followed but Ctrl+C on kubectl client should be detected by InterLink VK, API, and then Slurm, so that it stops reading logs files matching the session (if multiple kubectl logs of the same pods is running, and only one of them is interrupted by Ctrl+C, then only one tail should be released).

Environment

• Operating System:
• Other related components versions:

Steps to reproduce

Logs, stacktrace, or other symptoms

output

Summary of proposed changes