Fix(inquirer): Allow string choices (backward compat with v9 & prior)

[SBoudrias]

Ref #1527

Inquirer v9 & prior allowed choices to be array of strings. Given how widespread that pattern is, we should maintain this backward compatibility. It'll also simplify the work of folks migrating from inquirer to @inquirer/prompts with less code change.

TODO

• Select prompt
• Checkbox prompt
• Search prompt
• Rawlist prompt
• Documentation

[mshima]

I saw later that there is backward compatibility in place:

Inquirer.js/packages/inquirer/src/ui/prompt.mts

Lines 297 to 306 in ce5d3b6

	question.choices = choices.map(
	(choice: string | number | { value?: string; name: string }) => {
	if (typeof choice === 'string' || typeof choice === 'number') {
	return { name: choice, value: choice };
	} else if (!('value' in choice)) {
	return { ...choice, value: choice.name };
	}
	return choice;
	},
	);

.

It's possible to add to backward compatibility types only:

Inquirer.js/packages/inquirer/src/types.mts

Lines 50 to 57 in 9b77c67

	type AddStringToArrayType<T extends any[]> = (T[number] | string)[];
	type ArrayChoicesValueOrAsyncGetterFunction<T, A extends Answers> =
	T extends Record<'choices', any>
	?
	| AddStringToArrayType<T['choices']>
	| AsyncGetterFunction<AddStringToArrayType<T['choices']>, A>
	: never;

Of course if the string support is added to choices, the backward compatibility can be dropped.

[SBoudrias]

Ohh I forgot about that. I'll still bring it over to @inquirer/* since it makes migration easier.