Allow cloning of deleted assets

[snipe]

This cleans up a bit of confusing UI and also now allows users to clone deleted assets. We were inconsistent with our UI, allowing the clone button on the "Deleted Assets" page, but would just return an "asset not found" error, so it should have been disabled, or it should have worked.

I can see scenarios where you might want to clone a deleted item, so this PR makes it so that clicking "clone" on that asset will now bring up a normal clone page.

[what-the-diff]

PR Summary

• Refactoring AssetsController.php
  The code in AssetsController.php was streamlined by allowing the getClone method to directly accept an Asset object instead of an assetId. This modification enhances the efficiency and readability of the code. Furthermore, the view was updated to use the newly defined $cloned variable which now holds the attributes of the asset object.

• Improvising view.blade.php
  In view.blade.php, amendments were made to provide a more structured user interface. A new section was introduced, accompanied by a link for auditing assets. This link is displayed in specific conditions which will help the user with efficient asset management.

• Adjustments in the hardware.php route
  For better comprehension, the route {assetId}/clone was updated to use {asset}. This gives a more descriptive outlook of our route. Additionally, a new method, withTrashed, has been implemented, providing a view of deleted assets as well. Overall, this change enhances the maintainability and user understandability of the code.