fix: add a required input prompt for use in region input

[Amplifiyer]

Problem

Currently we accept "Enter" as acceptable input for region while configuring the profile. This results in "" value to be stored as region which later fails validation

Changes

fix: add a required input prompt for use in region input

Corresponding docs PR, if applicable:

Validation

Checklist

• If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
• If this PR requires a change to the Project Architecture README, I have included that update in this PR.
• If this PR requires a docs update, I have linked to that docs PR above.
• If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4a57977

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@aws-amplify/cli-core	Patch
@aws-amplify/backend-cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sobolk]

how about

    static input: (options: {
        message: string;
        defaultValue?: string;
        required?: boolean
    }) => Promise<string>;

above?

[sobolk]

(or some type union for options to make default and required mutually exclusive)

[Amplifiyer]

combining it was making it slightly cryptic without making a break in the API.

e.g.

{
    message: string;
    required: false;
    defaultValue?: string;
  } | {
    message: string;
    required: true;
  }

is a breaking change and

{
    message: string;
    defaultValue?: string;
  } | {
    message: string;
    required: true;
  }

allows both defaultValue and required shows up in the intellisense which is confusing API

await AmplifyPrompter.input({
    message: `Hit [enter] when complete`,
    required: true,
    defaultValue: ''
});

I figured having an explicit API is probably better to not touch the existing uses of input

[sobolk]

I did see this pattern in bedrock SDK. might be worth trying.

{
    message: string;
    required?: never;
    defaultValue?: string;
  } | {
    message: string;
    required: true;
    defaultValue?: never;
  }

[Amplifiyer]

ohh that's neat. Updated.