Add MayContainCustomFields Trait to Asset Update Request

[spencerrlongg]

Description

What it says on the tin, also added some null safe checks and fixed an issue with the trait that wasn't being used yet.

Type of change

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

How Has This Been Tested?

Test written

Test Configuration:

• PHP version: 8.1

[what-the-diff]

PR Summary

• Improved Custom Field Comparison Mechanism
  A modification was made in the file 'MayContainCustomFields.php'. This update improves how custom fields compare to the model's fieldset, taking into consideration null properties using a null-conditional operator.

• Added New Feature to UpdateAssetRequest
  The 'UpdateAssetRequest.php' file has been enhanced by incorporating the MayContainCustomFields trait. This addition aids in handling custom fields more efficiently during asset updates.

• Added Validations for Custom Field Updates
  In 'UpdateAssetTest.php', a new test method, 'testCustomFieldCannotBeUpdatedIfNotOnCurrentAssetModel', has been added. This method confirms that custom fields on asset models cannot be updated if they aren't present on the current asset model, helping to maintain data integrity.