Change user_id to created_by

[snipe]

Hooboy. This is a big one but it's been on my list for forever. We previously (foolishly) used user_id since literally v0.1-alpha, and then for consistency's sake, we kept going down that path. This touches an assload of files, and we're likely have to keep the admin value in the API responses for another version or two, but I think this makes a lot more sense in the bigger picture.

This also standardizes the scopeOrderByAdmin() and adminuser() methods.

[what-the-diff]

PR Summary

• Renamed 'admin' to 'adminuser' and 'user_id' to 'created_by' for Consistency
  The developers have updated various parts of the codebase, replacing the term 'admin' with 'adminuser' and 'user_id' with 'created_by'. This change was made for better consistency and standardization across the code.

• Enhanced Data Retrieval in the 'Api/AssetsController'
  The system's method of retrieving data in the 'Api/AssetsController' has been improved to include ‘adminuser’ and other relevant models.

• Updated Index Methods for New 'Created_by' Field
  The indexing methods in various areas of the code have been updated to work with the new 'created_by' field instead of the old 'user_id'. This update should improve the system's filtering and data display capabilities.

• Updated Action tracking
  Tracking of various actions in the application has been altered to use 'adminuser' instead of 'admin'. The ‘actionlogs’ relation has been updated accordingly, and the change would also aide in accurate action tracking.

• Updated Authorization Checks and Added New Relationships
  The developers have updated the authorization checks in the 'OauthClients.php' to verify against 'created_by' instead of 'user_id', and a new relationship 'adminuser' has been added in 'Accessory.php' - this connects accessories to their creator using 'created_by'.

• Renamed Relationships and Updated log actions
  Relationships were renamed from 'admin' to 'adminuser' in multiple models to reflect changes in how users are associated with records. Log actions in observers were updated to set 'created_by' instead of 'user_id' when logging actions.

• Upgraded User-Entity Associations
  Multiple files related to logging and tracking changes for User, Accessory, Asset, Company, Component, Consumable, and License factories were updated, with 'user_id' changed to 'created_by'. This improved the standard way the creating user is referenced.

• Improved Layout for Data Tables
  Fields such as 'created_by', 'created_at', and 'updated_at' have been added across various presenters, enhancing capabilities for searching, sorting, and displaying data.

• Refactored Code for Database Migration and Seeder Consistency
  The code was refactored to change 'user_id' to 'created_by' in the definition of multiple factories, including Department, Depreciation, License, Manufacturer, and Statuslabel. Moreover, seeders were updated to consistently use 'created_by' across varied models.

• Updated Assertions for Accuracy in tests
  The requirements specified in various tests have been updated, replacing 'admin' with 'adminuser', and 'user_id' with 'created_by'. This updates ensure test accuracy in light of the changes made in the application.

[uberbrady]

Once I got into the meat of this change, it started to seem very obviously superior to how we were doing it before - it's crystal-clear what the 'created_by' means and 'user_id' is still a little obtuse. So I think it's a great change! I did see a few other changes mixed in with this, and I still have to mention that it's much cleaner if we can have a big change like this just be the big change like this, and the other smaller changes be separated out. It's just 10x easier to review when we have that. I also still wonder if having 'createdBy' as the method name (which contains the relationship) corresponding to created_at as the column might be simpler? But, regardless of those nits, this is a great change and should really improve the "Developer Experience" (DX) on the product, as well as us from the support side being able to more quickly identify what various column names mean. Great job - a little scary, yes - but great!