Non-HTTPToken characters can be used in header names

[tsctx]

Bug Description

The following character "(),/:;<=>?@[\]{} is not allowed in the specification, but is allowed in Undici.

References:
https://fetch.spec.whatwg.org/#header-name
https://tools.ietf.org/html/rfc7230#section-3.2.6
https://tools.ietf.org/html/rfc9110#section-5.6.2

Reproducible By

There is a simple test.

// test.js
function pass(name) {
    try {
        return !!new Headers({ [name]: "test" });
    } catch (e) {
        return false;
    }
}

function assert(cond, message) {
    if (!cond) console.error(message);
}

function test() {
    for (const char of `"(),/:;<=>?@[\\]{}`.split("")) {
        assert(!pass(char), `The string \`${char}\` should throw an error.`);
    }
}

test();

Expected Behavior

The above test should succeed.

Logs & Screenshots

> $ node test.js
The string `"` should throw an error.
The string `(` should throw an error.
The string `)` should throw an error.
The string `,` should throw an error.
The string `/` should throw an error.
The string `:` should throw an error.
The string `;` should throw an error.
The string `<` should throw an error.
The string `=` should throw an error.
The string `>` should throw an error.
The string `?` should throw an error.
The string `@` should throw an error.
The string `[` should throw an error.
The string `\` should throw an error.
The string `]` should throw an error.
The string `{` should throw an error.
The string `}` should throw an error.

Environment

Windows 11
Node.js v21.1.0
Undici v5.27.2

Additional context

None