BREAKING(http/unstable): switch params and info args in Handler in route() for more conveniency

[lowlighter]

Closes #5884

Not sure if it qualifies for "breaking change" since the API is still unstable, but it does break apps relying on current implementation route()

As explained in the linked issue, since params: URLPatternResult is way more likely to be used than info: Deno.ServeHandlerInfo in non-default handlers, it makes sense to switch them for improved DX

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.52%. Comparing base (065296c) to head (4c43d31).
Report is 82 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6094      +/-   ##
==========================================
- Coverage   96.75%   96.52%   -0.24%     
==========================================
  Files         509      534      +25     
  Lines       39175    40976    +1801     
  Branches     5795     6134     +339     
==========================================
+ Hits        37905    39553    +1648     
- Misses       1228     1381     +153     
  Partials       42       42              

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

[kt3k]

LGTM.

There should be more usages for params than info in general. This change makes sense.

[kt3k]

We recently removed the dependency to (unstable) route in main of CLI (in deno init --serve). ref. denoland/deno#26595

I think we still need to wait for a while (at least a few versions of CLI releases) to land this PR to avoid the troubles.

[kt3k]

We've released 3 versions of CLI (2.1.0, 2.1.1, 2.1.1) which don't use unstable route function in deno init --serve output.

I think it's time we can land this.