Provide a convenient way to select the whole text with type()

Problem description

When using .type() I've been finding a common pattern that emerges is variations on the following

        await userEvent.type(titleInput, 'Edited title', {
          initialSelectionStart: 0,
          initialSelectionEnd: titleInput.value.length,
        });

To represent selecting the whole content and then overwriting it when typing

There was some related discussion in https://github.com/testing-library/user-event/issues/755#issuecomment-950689400

Suggested solution

Adding a new property like selectAll would be convenient, but probably opens up some awkward interactions if initialSelectionStart or initialSelectionEnd are also supplied.

From poking around in the code it looks like if I simply set a large value for initialSelectionEnd then it'll get clamped to the length of the input - which is basically what I want (although it's still quite verbose in a test). Perhaps the answer would be document the pattern of using a large number or Infinity as the selection end?

Additional context

No response

Start at the .type() entry point and trace how initialSelectionStart and initialSelectionEnd are handled, then review the related discussion in issue 755. Determine whether a concise whole-text selection option or documented selection-end pattern fits the existing API, and verify that typing replaces the complete input value without ambiguous option interactions.