Handle badly formatted last_audit_date in StoreAssetRequest

[marcusmoore]

Description

This PR follows up #14486 and handles users providing an non-dates for last_audit_date. The issue is Carbon will blow up trying to parse that field so I wrapped the parsing in a try/catch and if the value is not parsable I leave it alone so it can be picked up by the request's validation (the changes being made are in prepareForValidation()).

Huge thanks to @spencerrlongg for pointing this out.

Type of change

• Bug fix (non-breaking change which fixes an issue)

[what-the-diff]

PR Summary

• Implementation of new InvalidFormatException
  A new type of error, the InvalidFormatException, was introduced into StoreAssetRequest.php for better error handling.

• Refinement in prepareForValidation() method
  The prepareForValidation() method in StoreAssetRequest.php was updated to utilize a new function parseLastAuditDate(). This makes the process of modifying the last_audit_date more efficient and organized.

• New Method parseLastAuditDate()
  A new function, parseLastAuditDate(), was added into StoreAssetRequest.php. This method is purposed for parsing and formatting the last_audit_date field, improving the overall data management for this field.

• Added Validity Confirmation Test
  A new test, testNonDateUsedForLastAuditDateReturnsValidationError(), was implemented in AssetStoreTest.php. Its role is to check for validation errors when a non-date value is utilized for last_audit_date, ensuring the integrity and correctness of the data.