Formalize output structure

[bostrt]

The current data output structure is mostly a dump of files. We need to formalize the output structure as much as we can so third-parties consuming this plugin's output can rely on it.

Initial thoughts:

<root> ::= <meta> | <app-data>
<meta> ::= "oc-version" | "sos.log" | ...
<app-data> ::= <namespace> "/" <resource>
<resource> ::= <pod> | <events> | <status> | <all> | ...
<pod> ::= <pod-name> "/" <pod-resource> 
<pod-resource> ::= <pod-logs> | <pod-dc> | <pod-bc> | ...
<pod-logs> ::= "oc-logs-" <pod-name> "-" <container-name>
<pod-dc> ::= "oc-get-dc-" <app-name>
<pod-bc> ::= "oc-get-bc-" <app-name>
<events> ::= "oc-get-events"
<status> ::= "oc-get-status"

Example paths:

oc-sos-myproject-20180207-222734.tar.xz
/sos.log
/oc-version.txt
/myproject/django-ex-1-5cbrk/oc-logs-django-ex-1-5cbrk
/myproject/django-ex-1-5cbrk/oc-get-dc-django-ex
/myproject/django-ex-1-5cbrk/oc-get-bc-django-ex
/myproject/oc-get-events
/myproject/oc-get-status

[sferich888]

We should probably assume something like https://github.com/zerodayz/citellus/blob/master/README.md will be parsing the output.