Handle case where value is deleted in history

[snipe]

This is a sort of stopgap for #13710, which handles a few different cases

EOL Date will not show as changed if it was not actually changed anymore. It was being cast as a date which was really turning it into a date time

Encrypted fields will not show as changed if they're not really changed. We're still storing the change in history, since the encrypted value does change. This really needs to be handled in the controllers where we don't "save" those fields to the asset itself if nothing was changed.

And finally - the real reason I started this - this fixes an error where if a certain set of circumstances have occurred, an asset's history will look empty with an ErrorException: Attempt to read property "name" on null error. This would happen when the following happens:

1. Asset ABC had a location of 123.
2. Asset ABC gets edited to have a location of XYZ
3. Location 123 gets soft-deleted AND purged
4. Asset history is now broken

I'd really like to handle this better by actually capturing the "at that time" value when the asset is saved, to prevent people from sidestepping the history by editing Location 123 to be XYZ, without ever touching the asset. If the asset was changed, the location name/id at the time should be what we're logging, so we know that at that time, the location was named 123. But alas, that's an issue for a different PR.

[shortcut-integration]

This pull request has been linked to Shortcut Story #23473: Encrypted custom fields that are blank still show as changed.

[what-the-diff]

PR Summary

• Enhancement to Decryption Process in ActionlogsTransformer
  Changes have been made to the ActionlogsTransformer.php file where a new functionality has been added to decrypt and compare encrypted fields. To safeguard the process, a try/catch block is included to manage potential decryption exceptions. The system can now handle changes in custom encrypted fields and display the old and new values accordingly. Updates have also been made to handle changes in rtd_location_id and location_id.

• Data Type Update in Asset Model
  In Asset.php, the casts array, which is responsible for defining the data types of the model's attributes, has been updated. A boolean cast for eol_explicit has been added meaning this attribute will now be returned as a boolean value in the model. This offers a more accurate representation and easier handling of this data.

[uberbrady]

I think some small cleanups and this should help clean up a lot of the display-side of this problem - but I agree, it should probably be fixed on the creation-side, more thoroughly.