Replace untyped option maps with statically typed configuration objects

[shonfeder]

We are currently using a Map[String, Any] to store most of the application configuration. E.g., see

apalache/mod-infra/src/main/scala/at/forsyte/apalache/infra/passes/WriteablePassOptions.scala

Lines 23 to 24 in 98306ab

	class WriteablePassOptions extends PassOptions {
	private val store: mutable.Map[String, Any] = mutable.HashMap[String, Any]()

When values are fetched from the map, we need to do a runtime cast, which has also required carrying around typing information which could otherwise be erased:

apalache/mod-infra/src/main/scala/at/forsyte/apalache/infra/passes/WriteablePassOptions.scala

Lines 38 to 57 in 98306ab

	/**
	* Get a pass option
	* @param passName a pass name, or any other convenient name
	* @param optionName an option name
	* @return the option value, normally, an Integer or String
	*/
	def get[T: ClassTag](passName: String, optionName: String): Option[T] = {
	// The ClassTag prevents the type of `T` from being erased at runtime
	// See https://stackoverflow.com/a/18136667/1187277
	store.get(passName + "." + optionName) match {
	// Since we have added the ClassTag, we are able to match on its value here
	case Some(value: T) =>
	Some(value)
	case Some(value) =>
	throw new IllegalArgumentException(s"Option $optionName has unexpected type: " + value.getClass)
	case None => None
	}
	}

This makes the application configuration significantly more brittle than it needs to be, as it it subject to runtime errors due to illtyped configuration values or missing keys.

Afaict, we should be able to replace the untyped map with a class that provides static guarantees for the correct typing of the configuration values, and that any components that depend on configuration receive all values they need.

If we push all such configuration to the ConfigManager added in #1160, we'll also get the added benefit of being able to load and dump the full application configuration programmatically. The former should support automation, and the latter reproducibility, benchmarking, and debugging (e.g., the bug reports we generate could report a dump of the entire application configuration, which could then be loaded up trivially in regression tests).

---

We need to thread the statically specified options through our DI framework Guice. Here's the plan:

• Prepare the ApalacheConfig trait to communicate the override values of the options traits from ApalacheCommand #2038 after which the class ApalacheConfig will be used specify the values that can be be supplied to the options from the various configuration sources.
• Integrate all CLI options into the configuration management system #1177
• Implement class OptionsProvider for dependency injection #2040
• Integrate ConfigurationPassImpl into the configuration loading #2066
• Factor out CLI parsing from execution #2050

[shonfeder]

Closed by #2074