Issue: Add support for a catch-all on request() responder
Issue: Add support for a catch-all on request() responder: a task in LegoFlow-SWE (Harbor dataset). Problem Falcon returns a 405 Method Not Allowed response for any HTTP method that does not have a dedicated on <method () handler on a resource. There is no way to define a single fallback responder…
The task
**Problem** Falcon returns a `405 Method Not Allowed` response for any HTTP method that does not have a dedicated `on_<method>()` handler on a resource. There is no way to define a single fallback responder that handles all such unimplemented methods — every possible method must be enumerated explicitly.
Part of Lego-X/LegoFlow-SWE.