feat: Collect k8s events

[tolusha]

Signed-off-by: Anatoliy Bazko abazko@redhat.com

What does this PR do?

Collect k8s events as well as che logs.

The project structure:

.
├── events.txt
├── mkdir-workspacet93uo90gd1acw8zj
│   └── mkdir-workspacet93uo90gd1acw8zj.log
├── workspacet93uo90gd1acw8zj.che-jwtproxy-6454d8877b-5xp26
│   └── verifier.log
└── workspacet93uo90gd1acw8zj.go-cli-bf5459458-fgrdx
    ├── che-machine-execrbr.log
    ├── go-cli.log
    ├── theia-ide3j0.log
    └── vscode-goqsw.log

3 directories, 7 files

What issues does this PR fix or reference?

eclipse-che/che#15604

[sleshchenko]

@tolusha Seems this PR has conflicts against master branch.
Also, it could be useful if you add examples of folder structure we got as a result, along with file content examples (hint probably some info may be copied/pasted from the referenced issue description but I'm not sure if it's aligned to the implementation you provided).

[tolusha]

@sleshchenko It is ready to review

[sleshchenko]

Good valuable functionality.
There still a lot of places to be improved to provide better UX like:

• ask cheNamespace/workspaceName instead of workspaceId, like sleshchenko/java-mysql
• do not ask namespace since this information is available on Che Sever
  But it would require in MultiUser Che asking CheAccessToken, which is not easy to retrieve. And as we discussed offline, chectl login could help with it, but it's not really easy to do. We need to investigate it more and introduce something like context similar to that kubectl has.

So, I believe this is a great start point which can be improved later 👍
Please, consider registering the issues we discussed.