Added tests around asset check in and added missing actions to the api controller action

[marcusmoore]

Description

This PR adds tests around asset check-in via the web and API endpoints. In the process I added some missing actions that the web controller contained that were missing from the api controller:

• Migrating "legacy" locations from 0 to null/''
• Accepts the update_default_location=true field to update the asset's rtd_location_id to the provided location_id.
  • Note: the web controller already has this but uses 0 instead of true
• Clears pending checkout acceptances

I did some test organization and controller code clean up to make things a little easier to follow as well.

---

Something to note: providing a checkin_at via the web results in the action_date in the action log being {provided_date} 00:00:00. The api behavior differs by taking the provided checkin_at and adding the current time (if the request happens at 8:37:01am then the result is {provided_date} 08:37:01. Let me know if I should bring that behavior in sync.

---

Type of change

• Tests

[shortcut-integration]

This pull request has been linked to Shortcut Story #24808: Add tests around asset check in.

[what-the-diff]

PR Summary

• Enhancements to AssetFactory
  We have introduced a new feature to the AssetFactory class named assignedToUser(User $user = null). This improvement will allow the assignment of assets to specific users more efficiently.

• Changes to AssetCheckinTest File
  We've taken some restructuring steps for our test files. The old AssetCheckinTest.php file located in tests/Feature/Assets has been removed.

• Introduction of a New Test File
  A new test file called AssetCheckinTest.php has been added under tests/Feature/Checkins. This file includes several new testing methods:

  • testCheckingInAssetRequiresCorrectPermission() ensures that only users with the correct permissions can check in assets.
  • testAssetCanBeCheckedIn() verifies if the assets can be checked in as expected.
  • testCheckInEmailSentToUserIfSettingEnabled() confirms that a check-in email is sent if the function is enabled.
  • testCheckInEmailNotSentToUserIfSettingDisabled() tests that no email is sent if the sending email option is turned off.
  • testLastCheckInFieldIsSetOnCheckin() checks that the last check-in field is updated whenever an asset is checked in.