Decompose Cilium sysdump part into fine-grained components

[marseel]

Proposal / RFE

Currently we either run all Cilium tasks or we don't run any:

cilium-cli/sysdump/sysdump.go

Line 1390 in e04100b

if c.Options.CiliumNamespace != "" || c.Options.CiliumOperatorNamespace != "" {

Ideally, we would split these tasks into groups:

• Cilium-agent tasks that are run only if we detect cilium-agent
• Cilium-operator tasks that are run only if we detect cilium-operator
• Cilium-generic tasks like collecting CRDs CNP/CCNP, Cilium configmaps etc that are always collected if any of Cilium stuff is detected
• Hubble ...
• Clustermesh ...
• Envoy
• ...

And have similar logic to

cilium-cli/sysdump/sysdump.go

Lines 1593 to 1601 in e04100b

	tasks = append(tasks, c.getSPIRETasks()...)
	}
	if c.FeatureSet[features.GatewayAPI].Enabled {
	tasks = append(tasks, c.getGatewayAPITasks()...)
	}
	if c.FeatureSet[features.EnableEnvoyConfig].Enabled {
	tasks = append(tasks, c.getEnvoyConfigTasks()...)
	}

This would allow us to report a bit more concise output of what was/wasn't detected at the beginning of running sysdump, something like:

Cilium components detected:

• ✔️ Cilium Agent
• 🟥 Cilium Operator
• ✔️ Cilium CRDs detected: [...]
• 🟥 Cilium CRDs not detected: [...]
• ✔️ Hubble Relay
• ⚠️ Clustermesh - detected clustermesh-apiserver deployment, but no running pods
• ...

And then we wouldn't need to report all information for subtasks (like "Collecting ..." for things that don't exist) and only report ones that failed.

[github-actions]

This issue has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.

[github-actions]

This issue has not seen any activity since it was marked stale.
Closing.