ext:migrate now upgrades extensions

[inlined]

Nudges users to upgrade their extension before migrating. After the numbers of errors I ran into testing a migration of storage-resize-images@0.1.13 to 0.3.6, I'm of the belief that we might need to require this.

This PR required several fixes to the existing extensions code revealed by this particular upgrade. New features added to extensions over the years actually caused problems with the updated extensions. We now re-prompt for parameters if:

1. The parameter changed types (e.g. string -> SELECT_RESOURCE)
2. The parameter changed validators and the old type now fails
3. If the location system parameter is undefined (notably the only system parameter that is required). Short circuited if LOCATION was set previously
4. If any parameters are left over after upgrade, re-prompt for advanced parameters (e.g. in case there was a MAX_INSTANCES that is now a system parameter)

Fixing this also required fixing some other things like changing how sameParam matches, making sure the actual original version of the spec is fixed, and fixing the select prompt library which didn't handle --force correctly.

[gemini-code-assist]

Code Review

This pull request introduces the ext:migrate command to support migrating extension instances to function kits, along with updates to parameter prompting, validation, and default handling for multiselect parameters. The review feedback highlights several critical improvements: ensuring that checkbox prompts correctly use computed default options, propagating the --force flag to enforce non-interactive behavior across all sub-prompts, and safely handling potentially undefined instance.config.params to prevent runtime crashes during migration.

[gemini-code-assist]

In interactive mode, the computed default values for the checkbox prompt are ignored because inquirer.checkbox is called with the original opts instead of optsWithDefault. Reassigning opts directly ensures that both guard(opts) and inquirer.checkbox(opts) use the updated options with the correct defaults.

Suggested change

	let optsWithDefault = opts;
	if (opts.default === undefined && Array.isArray(opts.choices)) {
	const checkedValues = (opts.choices as Choice<Value>[])
	.filter((c) => c && typeof c === "object" && "checked" in c && (c as Choice<Value>).checked)
	.map((c) => c.value);
	optsWithDefault = { ...opts, default: checkedValues };
	}
	const { shouldReturn, value } = guard(optsWithDefault);
	if (opts.default === undefined && Array.isArray(opts.choices)) {
	const checkedValues = (opts.choices as Choice<Value>[])
	.filter((c) => c && typeof c === "object" && "checked" in c && (c as Choice<Value>).checked)
	.map((c) => c.value);
	opts = { ...opts, default: checkedValues };
	}
	const { shouldReturn, value } = guard(opts);

[gemini-code-assist]

When the --force flag is passed, the command should run completely non-interactively. However, because options.force is not propagated to sub-prompts (like parameter configuration), they will still prompt the user interactively. Setting options.nonInteractive = true and calling setNonInteractive(true) when options.force is active ensures that all prompts automatically fall back to their default values.

Suggested change

	.action(async (options: ExtMigrateOptions) => {
	const projectId = needProjectId(options);
	const plan = await createMigrationPlan(projectId, {
	package: options.package,
	extInstance: options.extInstance,
	extension: options.extension,
	nonInteractive: options.nonInteractive,
	force: options.force,
	});
	.action(async (options: ExtMigrateOptions) => {
	const projectId = needProjectId(options);
	if (options.force) {
	options.nonInteractive = true;
	const { setNonInteractive } = require("../prompt");
	setNonInteractive(true);
	}
	const plan = await createMigrationPlan(projectId, {
	package: options.package,
	extInstance: options.extInstance,
	extension: options.extension,
	nonInteractive: options.nonInteractive,
	force: options.force,
	});

[gemini-code-assist]

instance.config.params can be undefined in some older or malformed extension instances. Initializing finalParams to instance.config.params || {} prevents potential runtime TypeError crashes when accessing or modifying parameter keys.

Suggested change

	let finalParams = instance.config.params;
	let finalParams = instance.config.params || {};

[gemini-code-assist]

Pass finalParams (which is guaranteed to be defined) instead of instance.config.params to promptForNewParams to prevent a potential crash if instance.config.params is undefined.

Suggested change

	currentParams: instance.config.params,
	currentParams: finalParams,

[inlined]

Done.