toAnalyzerAnalysisKind

Value to pass to stig-code-analyzer --analysis-kind for this type. Defined by the v4 schema's codeAnalysisConfiguration.analysisKind enum:

• "data-and-control-flow" — sources at sinkASIL or above

• "cascading-faults" — sources strictly below sinkASIL

CONTROL_FLOW_ANALYSIS doesn't run a taint pass (it's the call-graph view), so it has no analyzer analysisKind — returns null and the caller is expected to not pass --analysis-kind for that mode.

Folder-name vs. CLI-value drift is intentional: the enum value CASCADING_FAILURE_ANALYSIS keeps the user-facing "failure" term (a domain word in functional-safety), while the v4 schema speaks "faults" for brevity. Both stay; this method bridges them.