Analyze Go ControlFlowGraph expected outputs

[Copilot]

The Go ControlFlowGraph .expected files were reviewed against main to check for CFG shape regressions from the old control-flow library.

• Expected-output comparison

  • Compared ControlFlowNode_getASuccessor.expected and NoretFunctions.expected with main.
  • Found no semantic CFG-shape differences requiring code or test updates.

• Result

  • No repository changes were needed; the current expected outputs already match main.

Original prompt

Look at the .expected files in go/ql/test/library-tests/semmle/go/controlflow/ControlFlowGraph/. Compare them to what they are on main, with the old control flow library. Do any of the current control flow graphs seem wrong? Make a list of issues that need to be addressed. Changes of names of nodes, or the number of nodes, are not important - it's the shape of the control flow graph that is important, and whether all aspects of control flow are captured correctly.

Created from VS Code.