Fix Web UI Merge Dialog Enter Should Submit

[nopcoder]

New code was tested manually by performing a Merge operation between branches.

Closes #8780

[github-actions]

E2E Test Results - Quickstart

[github-actions]

E2E Test Results - DynamoDB Local - Local Block Adapter

[itaigilo]

Actually, requesting changes for the Issue here (and not the PR):

Merge sounds like something to be considered carefully by the users.
I think that the friction added by having to click and not simply press Enter is better in this case.

What is the origin of this requirement? Is it something coming from users?
Maybe it's worth removing the Cancel-on-Enter behavior instead?

[nopcoder]

It came from frustration while working with UI and getting different experience from command and merge using the keyboard.

• Commit dialog -> Enter will commit the changes
• Merge dialog -> Enter will close the dialog and abort the change

The above aligned to commit, but if you think we should change both and require key combo to apply the change - I'm very open.

[nopcoder]

@itaigilo also not that usually in the UX the green button is the default, but I agree that in some dialogs, usually multi-line text, the enter will not trigger the button.

[itaigilo]

The above aligned to commit, but if you think we should change both and require key combo to apply the change - I'm very open.

@nopcoder my thoughts on this:

1. Merge and Commit are different actions, hence it well might be that we'll want that one will have more friction (i.e mouse-clicking) than the other.
2. In this case, I prefer that it's better to align both to do nothing when clicking Enter - but I also believe this should be a product decision.

[nopcoder]

@itaigilo as merge and commit both modify the branch by adding a commit (both we can revert) I will go with align the Enter for both commit and merge operations.