Make data connection bucket field mandatory

[DaoDaoNoCode]

Closes #1583

Description

Simply made the bucket field required.

How Has This Been Tested?

1. Go to data science project details page
2. Create a model server
3. Try to deploy a model, select New data connection, make sure the Bucket field is required
4. Try to leave it as blank, make sure you cannot click deploy button

Test Impact

Add some unit tests for isAWSValid function

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[DaoDaoNoCode]

@vconzola Can you check this very tiny change? I am not sure if it's necessary but it is a UI change, just add a small * at the end of Bucket field to indicate it's a required field.

[lucferbux]

@DaoDaoNoCode This is just for model serving, the goal is that in the main form Bucket is not mandatory but in model serving is required. The rest looks good, great testuite.

[lucferbux]

isRequired should only be mandatory in model serving

[lucferbux]

Maybe im wrong here but let me know @andrewballantyne @DaoDaoNoCode is that right?

[DaoDaoNoCode]

@lucferbux I confirmed with @andrewballantyne, you are right, it's only required here but not everywhere.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vconzola]

@DaoDaoNoCode LGTM. Thanks for asking. ;-)

[christianvogt]

/lgtm