packages/sosreport: Add kubectl top output in MetalK8s plugin

[TeddyAndrieux]

Example report

$ find . -name '*top.txt'
./sos_commands/metalk8s/flat/pod_ns_metalk8s-monitoring_top.txt
./sos_commands/metalk8s/flat/pod_ns_metalk8s-vips_top.txt
./sos_commands/metalk8s/flat/pod_ns_metalk8s-ingress_top.txt
./sos_commands/metalk8s/flat/pod_ns_metalk8s-logging_top.txt
./sos_commands/metalk8s/flat/pod_ns_metalk8s-ui_top.txt
./sos_commands/metalk8s/flat/pod_ns_kube-system_top.txt
./sos_commands/metalk8s/flat/node_top.txt
./sos_commands/metalk8s/by-namespaces/kube-system/pod/top.txt
./sos_commands/metalk8s/by-namespaces/metalk8s-ingress/pod/top.txt
./sos_commands/metalk8s/by-namespaces/metalk8s-logging/pod/top.txt
./sos_commands/metalk8s/by-namespaces/metalk8s-monitoring/pod/top.txt
./sos_commands/metalk8s/by-namespaces/metalk8s-ui/pod/top.txt
./sos_commands/metalk8s/by-namespaces/metalk8s-vips/pod/top.txt
./sos_commands/metalk8s/by-namespaces/_no_namespace/node/top.txt
./sos_commands/metalk8s/by-resources/pod/kube-system/top.txt
./sos_commands/metalk8s/by-resources/pod/metalk8s-ingress/top.txt
./sos_commands/metalk8s/by-resources/pod/metalk8s-logging/top.txt
./sos_commands/metalk8s/by-resources/pod/metalk8s-monitoring/top.txt
./sos_commands/metalk8s/by-resources/pod/metalk8s-ui/top.txt
./sos_commands/metalk8s/by-resources/pod/metalk8s-vips/top.txt
./sos_commands/metalk8s/by-resources/node/top.txt

[bert-e]

Hello teddyandrieux,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

[TeddyAndrieux]

/approve

[bert-e]

Integration data created

I have created the integration data for the additional destination branches.

• this pull request will merge improvement/add-kubectl-top-in-sosreport into
  development/127.0
• w/128.0/improvement/add-kubectl-top-in-sosreport will be merged into development/128.0

The following branches will NOT be impacted:

• development/123.0
• development/124.0
• development/124.1
• development/125.0
• development/126.0
• development/2.0
• development/2.1
• development/2.10
• development/2.11
• development/2.2
• development/2.3
• development/2.4
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• one peer

Peer approvals must include at least 1 approval from the following list:

• @ezekiel-alexrod

• @aprucolimartins

• @TeddyAndrieux

• @eg-ayoub

• @m4nch0t

• @ChengYanJin

• @JBWatenbergScality

• @thomasdanan

• @xaf-scality

The following options are set: approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/127.0

• ✔️ development/128.0

The following branches have NOT changed:

• development/123.0
• development/124.0
• development/124.1
• development/125.0
• development/126.0
• development/2.0
• development/2.1
• development/2.10
• development/2.11
• development/2.2
• development/2.3
• development/2.4
• development/2.5
• development/2.6
• development/2.7
• development/2.8
• development/2.9

Please check the status of the associated issue None.

Goodbye teddyandrieux.

The following options are set: approve