feature(locksmith): Update access control for checkoutConfigs

[0xTxbi]

Description

This PR introduces changes to transition the access control mechanism for checkout configurations from relying on the createdBy field to using lock managers.

Previously, a user could only list, or edit a checkout config if they were its creator. With this update, lock managers are now granted the ability to manage configurations for locks they control, even if they are not the original creators.

Key changes include:

• Allowing Lock Managers to save and manage configurations tied to locks they manage, regardless of who originally created the configuration.
• Listing configurations for users if they are a lock manager on at least one associated lock, even if they did not create the configuration.
• Refactoring the backend by separating logic into operations and controllers, improving organization.

Issues

Fixes #14248
Refs #14248

Checklist:

• 1 PR, 1 purpose: my Pull Request applies to a single purpose
• I have commented my code, particularly in hard-to-understand areas
• I have updated the docs to reflect my changes if applicable
• I have added tests (and stories for frontend components) that prove my fix is effective or that my feature works
• I have performed a self-review of my own code
• If my code involves visual changes, I am adding applicable screenshots to this thread

[julien51]

Let's talk about the way to list... because I don't think we can do that.

[0xTxbi]

Let's talk about the way to list... because I don't think we can do that.

sure thing!

[julien51]

More cleanup and changes...

[julien51]

If this throws then we need to handle it specifically at the controller level to return a 403

[julien51]

I think it would be nice to add tests here please