refactor(project): Always close CacheManager in BuildServer destroy

The active build promise can reject (e.g. when Cache=Force detects a stale
cache and throws). When destroy() awaited that promise, the throw skipped
the closeCacheManager() call below, leaving the SQLite cache.db handle
open. On Windows this caused subsequent tests to fail with EBUSY when
fs.rm tried to remove the buildCache directory.

Wrap the active-build await in try/finally so the cache manager is
released even when the build rejected.

Author: RandomByte

packages/project/lib/build/BuildServer.js

@@ -155,11 +155,17 @@ class BuildServer extends EventEmitter {
 		this.#destroyed = true;
 		clearTimeout(this.#processBuildRequestsTimeout);
 		await this.#watchHandler.destroy();
-		if (this.#activeBuild) {
-			// Await active build to finish
-			await this.#activeBuild;
+		try {
+			if (this.#activeBuild) {
+				// Await active build to finish
+				await this.#activeBuild;
+			}
+		} finally {
+			// Always release the cache manager, even when the active build rejected
+			// (e.g. Force-mode stale-cache errors). Otherwise the SQLite handle leaks
+			// and subsequent fs.rm of the cache directory fails with EBUSY on Windows.
+			this.#projectBuilder.closeCacheManager();
 		}
-		this.#projectBuilder.closeCacheManager();
 	}
 
 	/**