Hello folks, I am working on creating a library for use keto in Loopback4 (I have already done the same for kratos). I have a design choice that I would like to get your opinion on. As you may know, the @loopback/authorization package allows for the use of annotations to decorate controllers and methods with authorization information, such as resources, scopes, and allowed roles. My idea is to build upon this functionality by creating an extension that allows users to define their own authentication strategies, using these annotations to define the necessary tuples in a migration-like way. I am interested in your thoughts on this approach, as you have experience with both the ORY Keto and Loopback 4 projects. Do you think this is a viable approach, or do you have any suggestions for alternative approaches that might be more effective? @steep-lamp-91158 @gentle-thailand-50068