chore(libui): update ink (#6524)

## What's the problem this PR addresses?

While working on a yarn plugin (internal one), I noticed one of the yarn
packages had unmet peer dependencies.

```
➤ YN0000: @yarnpkg/plugin-interactive-tools@npm:4.0.0 [ae217] provides react@npm:16.14.0 with version 16.14.0, which doesn't satisfy the following requirements:

➤ YN0000: ink@npm:3.2.0 [64b23]                                          → >=16.8.0 ✓
➤ YN0000: react-reconciler@npm:0.26.2 [57218] → ^17.0.2  ✘

➤ YN0000: Note: these requirements start with ink@npm:3.2.0 [64b23]
```

This happened because inside Yarn, `ink`'s resolution is fixed due to
the patches to reduce the lodash size.
<!-- Describe the rationale of your PR. -->
<!-- Link all issues that it closes. (Closes/Resolves #xxxx.) -->

...

## How did you fix it?

This PR updates the libraries to the closet matching major version,
removing the peer errrors.
<!-- A detailed description of your implementation. -->

...

## Checklist

<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).

<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.

<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.

Author: BasixKOR