fix(middleware/cors): explicitly return No Content for the statusText when handling an OPTIONS request

[shawncarr]

When the cors middleware processes an OPTIONS request by default, it returns the response status text from the context, c.res.statusText. However, in most cases, the middleware is executed before any routes or other middlewares that could modify the response statusText, leading to a Not Found response status. To align with the explicit 204 being returned, the response should also include No Content, similar to how the etag middleware handles setting the statusText to Not Modified.

The author should do the following, if applicable

• Add tests
• Run tests
• bun run format:fix && bun run lint:fix to format the code
• Add TSDoc/JSDoc to document the code

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.70%. Comparing base (80c7e22) to head (e0c9f4e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3719   +/-   ##
=======================================
  Coverage   91.70%   91.70%           
=======================================
  Files         159      159           
  Lines       10165    10165           
  Branches     2919     2880   -39     
=======================================
  Hits         9322     9322           
  Misses        842      842           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[yusukebe]

Hi @shawncarr

Thank you for the PR. I think this is good.

@usualoma Can you review this?

[usualoma]

Hi @shawncarr, thank you.
LGTM!

[yusukebe]

LGTM!

[yusukebe]

@shawncarr @usualoma Thanks!

Merging now.