Redesigning the crucible-cli API

[langston-barrett]

The crucible-cli API is heavily callback-oriented. For example, it requires a callback for setting up the appropriate Crucible language extension:

crucible/crucible-cli/src/Lang/Crucible/CLI.hs

Lines 115 to 118 in 93bfa7f

	simulateProgramWithExtension
	:: (IsSyntaxExtension ext, ?parserHooks :: ParserHooks ext)
	=> (forall sym bak t st fs. (IsSymBackend sym bak, sym ~ ExprBuilder t st fs) =>
	bak -> IO (ExtensionImpl () sym ext))

and provides several "hooks" for code that does different things before the program is simulated:

crucible/crucible-cli/src/Lang/Crucible/CLI.hs

Line 69 in 93bfa7f

data SimulateProgramHooks ext = SimulateProgramHooks

This is a confusing API (due to the amount of inversion-of-control), and it is not very flexible. For example, it is currently impossible to set up Macaw's memory adequately. We should consider if there are alternative designs that would allow code reuse without resorting to a "framework-style" API.