Added tests for accessory api controller

[marcusmoore]

Description

This PR mainly focuses on tests for the accessories API controller and includes some dead code removal in the process.

Type of change

• Tests

[what-the-diff]

PR Summary

• Removed Access Control for Accessory Creation and Checkout
  The team removed the authorization check for creating accessories in the system. In addition, the checkout process got simpler with removal of access control based on companies. This change should make the system more efficient and user-friendly.

• Clean-up and Simplification
  Certain methods got simplified by removing unnecessary code. The checkin method under AccessoriesController for instance was overhauled to avoid improper handling of data and variables. Similarly, the logCheckin method in Loggable saw removal of unused codes related to settings retrieval. This would improve the performance of the software.

• Multi-User Checkouts in Accessory Factory
  A new method for allowing checking out accessories to multiple users was added to AccessoryFactory. This will enhance the software's overall usability.

• Additional Scripts for Functional Testing
  New test scripts were added like AccessoriesForSelectListTest and IndexAccessoryCheckoutsTest to verify and validate the software's ability to select accessories based on company and its retrieval capabilities. These tests will help ensure the software's accuracy and dependability.

• Enhanced Testing for Accessory Management
  The team made enhancements to the test scripts pertaining to accessory management. These include changes to the existing index and update accessory tests to implement company scoping and allow successful accessory updates, and the addition of new store and checkin accessory tests for validating and storing accessories with required fields. This will make sure your software works in a reliable way and as expected, especially when managing accessories.

• Further Testing Enhancements
  Additional tests were created to confirm the functionality of checking in accessories, the adherence to multi-company support scoping, and to verify the check-in logs. This should improve the software's robustness and reliability.

• Improved Test Method Naming and Implementation
  Checkouts related test method was renamed for better clarity and the TestsPermissionsRequirement interface was applied for a consistent way of handling permissions. This should make the software more maintainable and easy to understand.

• Added Functionality in Custom Test Macros
  A new feature was included in Custom Test Macros to check if response messages contain certain keys, providing a further layer of testing precision. This should improve the ability to quickly identify and fix any issues.

[snipe]

We should probably make those tests pass 😂