feat(middleware_factory): support router

[BVMiko]

Issue #, if available:
#953

Description of changes:

The changes needed for lambda_handler_decorator to support routers are only to modify the arguments of the inner wrapper and its invocation, so I modified it to accept arbitrary arguments.

Due to the difference in signature (and function name), it may be preferable to instead move this to a clone named router_decorator instead of modifying the original lambda_handler_decorator. If you would like me to do so, let me know and I can make the change.

Checklist

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

Breaking change checklist

There may be potential issues with positional arguments if we reuse the same decorator.

RFC issue #:

• Migration process documented
• Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[heitorlessa]

Could you duplicate the decorator factory into a new function named decorator?

That will prevent confusing anyone reading someone's else coding that uses both of them in different ways. It's also easier to update the docs with a new section as the more explicit we are.

Thank you so much.

[heitorlessa]

following up in case you missed the comment above

[leandrodamascena]

Hi everyone! We are working on issue #1955 to add router support to Middleware Factory and other changes.

As this PR has not been updated for some time and issue #1955 will add this support and some other improvements, so we are closing this PR.

Thank you all and if you think that something can be done in this PR, feel free to reopen it.