Accessory checkin via API reported wrong target user

[uberbrady]

Fixes [fd-34518]

We were reporting the user_id of the accessories_users table, when we wanted to report the assigned_to instead. user_id is the identity of the Admin doing the thing.

I need to test this before I can sign off on it, so I'm leaving it at draft - but I'll run a couple of API tests against my instance and see if this fix does fix the bug. Then I'll take it off of Draft.

[what-the-diff]

PR Summary

• Modification in Accessory Controller
  The way we keep track of actions related to accessories has been changed. Instead of using the user_id, we shifted to using assigned_to property of the accessory_user. This will provide a more accurate tracking of actions.

• Update in Log Checkin Method
  The logCheckin method, responsible for logging when items are checked in, is now using the above modified variable. This enhances the logging accuracy and data reliability.

• Improved Record Deletion
  We introduced a way to delete a specific record from accessories_users table. Now, when needed, we're able to remove the record where the id equals the accessory_user's id. This further increases the flexibility and control over accessory user-related data.

[uberbrady]

Okay, I've tested this now - without my change, I can confirm that the 'target' is set to the admin user (not the actual user that it was checked out to. With my change, it is correctly the actual targeted user.

So this is now good to go.

[snipe]

You targeted this to master :( I didn't notice before I merged it