bug: kit run-tests does not work with the app framework

[Gohlub]

Describe the bug
The ongoing changes in the app framework and hyperprocess macro have broken the testing framework. I did some digging but I think I need to look into run-tests module for more detail. Overall, based on my observation, the issue seems to be with the testing package /target directory, which is separate from the main package /target directory (maybe we want to consolidate all of them to be in /target?). Nevertheless, there seems to be multiple elements to this bug (which I think are all artifacts of the fact that we just didn't handle tests when working on the app framework after Luc left), but the issues are:

• The testing package WIT is not being generated, making the test package build to fail
• There seem to be some issues with caller utils and how they are imported in the testing package (probably related to build: consolidate target dir into one at package level #314 since that changed the origin caller utils.

I don't recall correctly, but I did manage to solve the first problem by hard coding the WIT file (but it still fails to build due to dependency issues). The second problem, however, is downstream of the #314 pull request (I think).

Nick mentioned that kit does stuff lazely, but in this case since tests depend on caller_utils, we might need to bundle the WIT generation at least.

Otherwise, running kit run-tests should fail if the main package hasn't been built.

To Reproduce
Steps to reproduce the behavior:

1. Go to https://github.com/Gohlub/hyperprocess-template
2. Clone it, and run kit b -hyperapp and kit run-tests

[nick1udwig]

If paths are messed up by #314, which seems plausible, that seems like the real issue

Otherwise, running kit run-tests should fail if the main package hasn't been built.

run-tests always builds dependency packages THEN setup packages (like the "main package" that is going to be tested) THEN the test package (i.e. if the package is foo and the test package it foo-test, foo is always built first when specified as a "setup package"), Then foo-test is built:

this is where we build packages:

kit/src/run_tests/mod.rs

Line 701 in 62a6af3

build_packages(&test, test_dir_path, &detached, &persist_home, runtime_path).await?;

we build deps, then setups, then tests:

kit/src/run_tests/mod.rs

Lines 359 to 437 in 62a6af3

	for dependency_package_path in &test.dependency_package_paths {
	let path = match expand_home_path(&dependency_package_path) {
	Some(p) => p,
	None => test_dir_path
	.join(&dependency_package_path)
	.canonicalize()?,
	};
	debug!("Build {path:?}");
	build::execute(
	&path,
	false,
	false,
	&HashSet::new(),
	&HashSet::new(),
	false,
	"test",
	Some(url.clone()),
	None,
	None,
	dependency_package_paths.clone(),
	vec![], // TODO
	false,
	test.hyperapp.unwrap_or_default(),
	false,
	false,
	false,
	false,
	)
	.await?;
	debug!("Start {path:?}");
	start_package::execute(&path, &url).await?;
	}
	for setup_package in &setup_packages {
	build::execute(
	&setup_package.path,
	false,
	false,
	&HashSet::new(),
	&HashSet::new(),
	false,
	"test",
	Some(url.clone()),
	None,
	None,
	dependency_package_paths.clone(),
	vec![], // TODO
	false,
	test.hyperapp.unwrap_or_default(),
	false,
	false,
	false,
	false,
	)
	.await?;
	}
	for test_package_path in &test_package_paths {
	build::execute(
	&test_package_path,
	false,
	false,
	&HashSet::new(),
	&HashSet::new(),
	false,
	"test",
	Some(url.clone()),
	None,
	None,
	dependency_package_paths.clone(),
	vec![], // TODO
	false,
	test.hyperapp.unwrap_or_default(),
	false,
	false,
	false,
	false,
	)
	.await?;
	}