feat: add Method/Route logging in exceptionHandler()

[kenjis]

Description
See https://forum.codeigniter.com/showthread.php?tid=88724&pid=413505#pid413505

• add HTTP method and Route in Exception logging

E.g.,

CRITICAL - 2023-10-27 21:16:26 --> Allowed memory size of 8388608 bytes exhausted (tried to allocate 20971552 bytes)
[Method: GET, Route: /]
in APPPATH/Controllers/Home.php on line 9.
 1 [internal function]: CodeIgniter\Debug\Exceptions->shutdownHandler()

CRITICAL - 2023-10-27 21:16:49 --> Allowed memory size of 8388608 bytes exhausted (tried to allocate 20971552 bytes)
[Method: GET, Route: test]
in APPPATH/Controllers/Home.php on line 9.
 1 [internal function]: CodeIgniter\Debug\Exceptions->shutdownHandler()

CRITICAL - 2023-10-27 23:23:20 --> Allowed memory size of 8388608 bytes exhausted (tried to allocate 10485792 bytes)
[Method: CLI, Route: app:sample]
in APPPATH/Commands/Sample.php on line 59.
 1 [internal function]: CodeIgniter\Debug\Exceptions->shutdownHandler()

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide

[MGatner]

This is a cool and helpful feature but it introduces an error-handling dependency on our Request service which (generally speaking) seems like a bad idea. I see you've already handled some potential niche cases, like CLI, but I would like hear thoughts from more of the team.

On closer inspection, this dependency already exists and you barely moved it earlier in the code. 🤦‍♂️ Don't mind me. Definitely a handy feature, let's go.

[kenjis]

@MGatner It is a good view point. We should avoid unneeded dependencies.
However, I think it is acceptable for the exception handler dependency on Request.