Filter not supported verbs by interactive kubectl, improve telemetry for interactive Slack messages

[pkosiec]

Description

Changes proposed in this pull request:

• Filter not supported verbs for interactive kubectl (currently it is not used, but @mszostok will switch to actual Command Guard in one of the next PRs)
• Implement telemetry for actionable messages
• Add missing telemetry to help and feedback typed commands
• Fix "invalid verb" problem for the edit command, even if the verb is valid

Testing

To test against real Segment, contact me 🙂 Alternatively, you can test it with fake reporter with the following instruction:

Check out this PR.
Replace noop_reporter.go ReportCommand method with:

// ReportCommand reports a new executed command. The command should be anonymized before using this method.
func (n NoopReporter) ReportCommand(a config.CommPlatformIntegration, b string, c command.Origin) error {
	// TODO: Remove
	fmt.Printf(">>> Reported command: %s/%s/%s\n", a, b, c)
	return nil
}

Run Botkube locally:

export KUBECONFIG=...

export BOTKUBE_SETTINGS_LOG_LEVEL=info
export BOTKUBE_SETTINGS_KUBECONFIG=$KUBECONFIG
export BOTKUBE_CONFIG_PATHS="$(pwd)/resource_config.yaml,$(pwd)/comm_config.yaml"
go run cmd/botkube/main.go

Play around with different commands and see what is reported. Test:

• actionable messages (you can use the sample YAML from the testing instruction of the Make event notifications actionable #803 PR)
• interactive kubectl
• edit source bindings
• help command
• feedback command (both button from help and typed command)

Separate PRs

• Add delete confirmation for message action
• Documentation

Related issue(s)

#786

[pkosiec]

Pull request rebased - added support for plain text command origin 🙂