Added tests around asset checkout

[marcusmoore]

Description

This PR adds tests around asset checkout via the web and API. It also includes a small test to ensure the LogListener handling a onCheckoutableCheckedOut event results in an entry in the action_logs table.

The only real change to application code, besides removing some extra whitespace, is in the AssetCheckoutRequest where the rules nullable and date were added for checkout_at and expected_checkin.

The test scenarios (methods in this case) between the two test cases are the same but the testLicenseSeatsAreAssignedToUserUponCheckout and testCannotCheckoutAcrossCompaniesWhenFullCompanySupportEnabled for the API is marked as incomplete since that behavior exists in the web but not in the API.

• ❓ Should I update the API controller to match that behavior in this PR or in a follow up?

I'm opening this against develop but I'm totally fine with this being moved to draft until after v7.

Type of change

• Tests

[what-the-diff]

PR Summary

• Enhanced Validation for Checkout Dates
  The rules for validating checkout and expected check-in dates for assets have been improved. This is to ensure that the dates entered are valid and accurately represent the expected timelines for when these assets are being used.

• New Method to Assign License Seats
  A new function has been introduced that allows a license seat to be assigned to an asset. This makes tracking usage and availability of licenses simpler and more efficient.

• New Functionality to Confirm Deployability
  A new function called "readyToDeploy" has been introduced to check if certain assets are ready for deployment. This function helps teams to better manage their resources and to prevent any delays due to unavailability of resources.

• Enhanced Testing Framework
  Several new test files have been added; AssetCheckoutTest under the Api/Assets and Feature/Checkouts sections, and LogListenerTest under the Unit/Listeners section. Additionally, many changes have been made to test methods in these files. These serve to provide a more robust testing framework for the application, resulting in more reliable software updates.