Refactored due/overdue for audit, added due/overdue for checkin API endpoint and GUI

[snipe]

Whew. This got a lot messier and bigger than I had intended.

• Refactors the /api/v1/hardware/audits/due and /api/v1/hardware/audits/overdue endpoints
• Added the /api/v1/hardware/checkins/due and /api/v1/hardware/checkins/overdue endpoints
• Added the /api/v1/hardware/checkins/due-or-overdue and /api/v1/hardware/audits/due-or-overdue endpoints
• Removed duplicate api/v1/hardware/audit/due API routes that somehow snuck through (they have been there a while)
• Added a UI interface for the new due/overdue checkins
• Added badge numbers to the sidebar with counts for checkins and audits
• Changed the badges to be more consistent with our other badges
• Changes the Due for Audit UI into a tabbed interface so we can have both Due/Overdue for Audit and Checkin without adding too much more stuff to that side menu
• Updated notifications to use the same scoping for consistency
• Added tests

By expanding out the existing index API, it means we can still filter/sort/search/etc on these new endpoints the same as we can for any other asset listing page.

To do eventually:

• Refactor the Notifications for expected checkins to use the new model scopes.
• See if we can't make that sidenav hover width a little bigger for less wrapping

[what-the-diff]

PR Summary

• Enhanced Assets Controllers
  The Main API AssetsController has been refined to handle due and overdue audits and checkin dates. The main AssetsController has some methods revamped to be more focused on checkin-related tasks. Previous methods have been made simpler and clearer.

• Updated Middleware for Asset Count
  Several new metrics have been added for view's sidebar in AssetCountForSidebar middleware, including those concerning audits and checkins both due and overdue, enhancing overall ease of navigation and tracking.

• Extended Functionality in Asset Model
  The Asset model has been enhanced to be more encompassing with methods for daily checkins, overdue checkins and overall due or overdue checkins, making its utilisation robust.

• Modification in Public UI files
  UI changes have been incorporated in app.css, overrides.css, and all.css with a new rule for sidebar menu styling resulting in improved aesthetics.

• Update in Translation File
  Two additional translations added, concerning audit due days and checkin due days, leading to clearer communication with users.

• Improved Views
  The view audit-dure.blade.php has been updated with improved navigation and data attribute handling providing a better user experience. The file audit-overdue.blade.php has been removed, replaced by an added file checkin-due.blade.php.

• Updated Layout
  The default layout file now displays badges with more relevant data, thus helping users know the status of their assets at a glance with the incorporation of badges.

• API Routes Update
  New API endpoint added to fetch upcoming audits and checkins along with the removal of duplicate endpoints. This would help in reducing redundancy and improving system efficiency.

• Web Routes Management
  The web routes for the hardware has been cleaned up by removing redundant code, making the system lighter and faster.

• Test Feature Changes
  Test names are more descriptive now and new tests for API endpoints have been added to cover all possible sceneries. The refactoring of tests leads to better code coverage and potential problem identification.

[marcusmoore]

I'm just diving in but I wanted to share this first:

I think we can increase confidence in these tests by creating an asset(s) in each "status" and then querying to make sure we only get back the ones expected. So the outline for a test might look like

1. Create an asset that has upcoming audit
2. Create an asset that is overdue for audit
3. (maybe) Create an asset in another state that shouldn't show up?
4. Send queries with upcoming_status set to overdue, due-or-overdue, due
5. Check if the asset ids you expect from the assets created above are included and the ones that shouldn't be included aren't.

The increased confidence comes from knowing the test created assets that shouldn't be returned and checking that they weren't.

[marcusmoore]

I did a pure-code review and found a couple changes. Going to pull it up and fully test in a browser soon.