fix: implicit_authorization on default authorization service

[Paul-Bob]

Description

Fixes #3327

Ensure that implicit_authorization doesn't impact community apps without custom authorization service

Apply implicit_authorization only when using a custom authorization service or the Avo::Pro::Authorization::AuthorizationService.

If the default Avo::Services::AuthorizationService is being used, bypass the implicit_authorization logic entirely.

In summary, implicit_authorization should only take effect if a custom authorization service is implemented or when using Avo Pro.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[codeclimate]

Code Climate has analyzed commit 1a5c796 and detected 0 issues on this pull request.

View more on Code Climate.

[github-actions]

This PR has been merged into main. The functionality will be available in the next release.

Please check the release guide for more information.

[davegson]

thanks a lot for your issue and the fix! 🚀 took me some painful hours to understand why as: :has_many just was not working...

[Paul-Bob]

That certainly wasn’t a pleasant experience, it’s fixed on >= v3.13.7

Still has an impact on applications where Avo was installed on a version between v3.13.4 and v3.13.6.

Upgrading to >= v3.13.7 fixes it.