Refactor prepare task to use typed inputs and outputs

[justin-thurman]

Follows

#1302

Description

This PR continues the migration of CLI tasks to the new, typed structure established in #1302, migrating the prepare task. Like the initialize task refactored in #1323, this task has distinct subtasks, which I've split up into separate files to aid readability. So the commits in this PR are structured around migrating each of these subtasks separately, alongside some generic housecleaning. The main prepare/index.ts orchestration layer is updated throughout the other commits (I couldn't find a clean way to put this in its own commit, unfortunately, so I recommend reviewing prepare/index.ts primarily in its finished state and not worrying too much about its state commit-by-commit).

📦 Published PR as canary version: 16.10.2--canary.1324.25933365397.0

✨ Test out this PR locally via:

npm install chromatic@16.10.2--canary.1324.25933365397.0
# or 
yarn add chromatic@16.10.2--canary.1324.25933365397.0

[github-actions]

📦 Package Size: 7100 KB
✅ Compared to main: 0 KB 354b119 (7100 KB)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.77%. Comparing base (354b119) to head (c1ed781).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1324      +/-   ##
==========================================
+ Coverage   80.75%   80.77%   +0.02%     
==========================================
  Files         224      224              
  Lines        4204     4235      +31     
  Branches     1200     1203       +3     
==========================================
+ Hits         3395     3421      +26     
+ Misses        695      694       -1     
- Partials      114      120       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[aikido-pr-checks]

Potential file inclusion attack via reading file - medium severity
If an attacker can control the input leading into the ReadFile function, they might be able to read sensitive files and launch further attacks with that information.

Show fix

Suggested change

	const apkPath = path.join(sourceDirectory, 'storybook.apk');
	const resolvedBase = path.resolve(sourceDirectory);
	const resolvedTarget = path.resolve(resolvedBase, 'storybook.apk');
	const relative = path.relative(resolvedBase, resolvedTarget);
	if (relative.startsWith('..') || path.isAbsolute(relative)) {
	throw new Error('Invalid file path');
	}
	const apkPath = resolvedTarget;

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}

[aikido-pr-checks]

Potential file inclusion attack via reading file - medium severity
If an attacker can control the input leading into the ReadFile function, they might be able to read sensitive files and launch further attacks with that information.

Show fix

Suggested change

	const buildLog = readFileSync(input.buildLogFile, 'utf8');
	const buildLogFile = input.buildLogFile;
	if (buildLogFile.includes('..') || path.isAbsolute(buildLogFile)) {
	throw new Error('Invalid file path');
	}
	const buildLog = readFileSync(buildLogFile, 'utf8');

_{Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}