This change updates the project structure to become flattened.
Previously, the simulator, frontend and API each lived into their own
directory.

With this change, all modules of the project live in the top-level
directory of the repository. This should improve discoverability of
modules of the project.

This change adds a power model for optimizing the mean squared error 
to the available power models in OpenDC.

This change introduces the SimulationCoroutineDispatcher implementation which replaces the TestCoroutineDispatcher for running single-threaded simulations.

This change migrates the remainder of the codebase to the
SimulationCoroutineDispatcher implementation.

This change introduces the SimulationCoroutineDispatcher implementation
which replaces the TestCoroutineDispatcher for running single-threaded
simulations.

Previously, we used the TestCoroutineDispatcher from the
kotlinx-coroutines-test modules for running simulations. However, this
module is aimed at coroutine tests and not at simulations.

In particular, having to construct a Clock object each time for the
TestCoroutineDispatcher caused a lot of unnecessary lines. With the new
approach, the SimulationCoroutineDispatcher automatically exposes a
usable Clock object.

In addition to ergonomic benefits, the SimulationCoroutineDispatcher is
much faster than the TestCoroutineDispatcher due to the assumption that
simulations run in only a single thread. As a result, the dispatcher
does not need to perform synchronization and can use the fast
PriorityQueue implementation.

This change adds a quick workaround for getting kotlinx-benchmark to
work again with Gradle 7.
See https://github.com/Kotlin/kotlinx-benchmark/issues/39.

This change fixes and issue where a SimWorkload was being re-used across
simulation runs. Given that SimWorkload is stateless, this may cause
strange issues.

This change modifies the web runner to construct the topology only once
per repeat, given that the construction does not depend on the repeat
number.

This change fixes an issue where incorrect scheduling weights were
applied to the filter scheduler.

This change introduces the SimProcessingUnit which represents a
simulated processing unit which the user can control during the workload
execution.