* Ignore some contents of the .yarn directory

* Rename input.spec.js to input.spec.jsx

* Remove @testing-library/react-hooks

* Update tests which use the data-testid attribute to query the span
  element.
* Replace the getByTestId queries with getByText and check if the span
  expected to contain the text is visible.

* @testing-library/jest-dom
* @testing-library/react
* jsdom
* vitest

* Remove instances of getCustomEvent and use simulateKeyInput instead.

* Replace user.keyboard from `@testing-library/user-event` with
  user.type which seems to be better suited for inserting text in input
  fields (https://testing-library.com/docs/user-event/utility#type).

* Some tests don't work with `user.type` method provided by
  @testing-library/user-event (v14). The updated wrapper function
  `simulateKeyInput` accepts an additional argument - options - which
  can be used to specify that the `user.keyboard` method should be used
  instead.
* Every test which works with one of `user.type` or `user.keyboard` and
  not the other has been manually tested to confirm that the component
  being tested exhibits the correct/expected behaviour.

* Some tests were commented out during migration to the new testing
  setup. All such tests have now been added back.

* The positive assertion makes more sense while still covering the
  negative assertion case.

* Key input now directly uses @test-library/user-event to type text into
  the input element being tested. Previously, in some cases, the
  function used `fireEvent.change` to update the value of the input
  element with a pre-computed value.
* This change does not extend to "special keys" such as `Backspace` or
  `Delete`.

* The test now uses the `simulateKeyInput` function to set
  `input.selectionRange`. Pressing any key then replaces the selected text
  inside the input element.

* Added functions to select text inside an input element by, 1) double clicking
  inside it at a given position, and 2) pressing and dragging the mouse cursor.

* If `selectionEnd` is undefined, it is set to `selectionStart`, which
  matches the behaviour of `simulateKeyInput` function.
* It also uses other functions to select text inside the input element
  instead of directly setting the `selectionRange`.

* The other `simulateFocus` should ideally be used only when necessary
  as clicking to focus handles the more general cases when the user
  takes an action to focus the input element.

* Add the todo annotation to four tests that are currently failing.
  These tests have been confirmed to fail in a browser upon manual
  testing.
* Fix incorrect assertion in a test.

* Add a workaround to handle cases where `input.selectionStart !=
  input.selectionEnd` by first removing the selected text in the input
  and then using `user.keyboard` to type the key pressed.

* Update node version.
* Use the latest versions of setup-node and checkout actions.
* Use `--frozen-lockfile` flag when running `yarn install`.
* Update script to run the new test suite.

- Added better way to find change range which fixes  issue around duplicate subsequent characters giving incorrect change range.
- Remove findChangedIndex util, as it wasn't used anywhere.
- Fix simulateKeyInput util
- Fix incorrect test
- Fix issue when complete text is selected and replaced with new value in pattern format. It was it was incorrectly pasting value.