Bug: Evalite Creates Cache Directory Regardless of `cacheEnabled` Setting

Description

Evalite unconditionally creates the cache directory at node_modules/.evalite/files/ during initialization, even when cacheEnabled: false is explicitly set in the configuration. This causes failures in read-only filesystem environments like AWS Lambda.

Root Cause

In run-evalite.js, the runEvalite() function creates the files directory before checking the cacheEnabled option:

export const runEvalite = async (opts) => {
    const cwd = opts.cwd ?? process.cwd();
    const filesLocation = path.join(cwd, FILES_LOCATION);  // Line ~135
    await mkdir(filesLocation, { recursive: true });       // Line ~136 - UNCONDITIONAL!
    
    // ... 170+ lines later ...
    
    const cacheEnabled = opts.cacheEnabled ?? config?.cache ?? true;  // Line ~177

The FILES_LOCATION is hardcoded in backend-only-constants.js:

const CACHE_LOCATION = path.join("node_modules", ".evalite");
export const FILES_LOCATION = path.join(CACHE_LOCATION, "files");

Impact

This prevents evalite from running in environments with read-only filesystems, such as:

• AWS Lambda (where only /tmp is writable)
• Docker containers with read-only root filesystems
• CI/CD environments with restricted filesystem permissions