fix: Add support for passing authorization_scopes on routes with JWT authorizer

[jschilperoord]

Description

Make it possible to pass the authorization_scopes as a comma separated string on the integration level. Passing it as a set of string like the AWS resource expects makes the variable validation fail with a " attribute types must all match for conversion to map" as also described here

Motivation and Context

Due to missing documentation on the AWS provider the authorization_scopes parameter was being ignored. The docs have been updated as seen here This fixes issue

Breaking Changes

No. This is an optional parameter

How Has This Been Tested?

• [x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
• [x] I have tested and validated these changes using one or more of the provided examples/* projects
• [x] I have executed pre-commit run -a on my pull request

[antonbabenko]

This PR is included in version 1.6.1 :tada:

[tim0git]

Amazing work, works like a dream! Thank you all.

[github-actions[bot]]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.