Added the ability to bulk print users

[marcusmoore]

Description

This PR allows printing all assigned items for multiple users via the bulk actions menu on the user index page.

---

Here's what will be rendered in the browser:

---

And bringing up the print dialog will put all of the users on a separate page:

---

• ❓ but ...should I update the column selector to do the same? It currently only affects the current table unless the page is refreshed:
  

---

Some additional details...

I updated the existing template, users.print, to accept multiple users and render them in a foreach on the front end.

When rendering multiple users I added a button to the top of the page to show and hide all of the EULAs on the page so they can be included in printing:

---

Partially addresses sc-18607

---

Type of change

• New feature (non-breaking change which adds functionality)

[what-the-diff]

PR Summary

• Improvement of the printInventory feature
  The printInventory function, found in our software's UsersController, has been enhanced. Now it loads related data from 'assets,' 'accessories,' 'consumables,' and 'licenses' in a single go. We also streamlined the way it displays data, making it easier to understand and read.

• Introduction of printAllThings feature
  We've added a new function, printAllThings, also to the UsersController. This function aggregates data about all users and their connected data in one place, providing a comprehensive overview.

• New access path print-all-things
  To make the new printAllThings function accessible, we've created a route titled print-all-things. Use this route to quickly gather all user-related data.

• Creation of print-shell.blade.php template
  A new display template, print-shell.blade.php, has been created to visually present user data. This template includes all necessary styles and scripts for it to look good and work efficiently.

[marcusmoore]

Not positive about this since the top of the controller method has $this->authorize('update', User::class);...might end up in a place where the user has access to view users but not update them?

Or maybe I should make this $this->authorize('view', User::class);?

[snipe]

I think we can start with $this->authorize('view', User::class); and add the stronger gates within that faux-router controller method.

[marcusmoore]

@snipe this is ready for a review. Please check out my question in the description noted with the ❓ and my review comment.