Bumps [undici](https://github.com/nodejs/undici) from 5.22.1 to 5.28.3.
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v5.22.1...v5.28.3)

---
updated-dependencies:
- dependency-name: undici
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

…ci-5.28.3

Bump undici from 5.22.1 to 5.28.3

Bumps [undici](https://github.com/nodejs/undici) from 5.28.3 to 5.28.4.
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v5.28.3...v5.28.4)

---
updated-dependencies:
- dependency-name: undici
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>

…ci-5.28.4

Bump undici from 5.28.3 to 5.28.4

* Fix cast logic

There's a lot to unpack here, but the tl;dr is to refer to the charset
ultimately to determine if the data is UTF8, if it is, we can decode it
to a UTF8 string.

This fixes behavior around CHAR/TEXT fields with a binary collation,
being surfaces as BINARY/BLOB types by MySQL.

For all intents and purposes, BLOB/BINARY/CHAR/TEXT are all effectively
identical and interchangeable, the only differentiator is their charset.
Either they are a UTF-8 charset, or a binary charset or some other
charset.

Fixes #169

---------

Co-authored-by: Ayrton <git@ayrton.be>