Add next_audit_date to the AssetsController logic

[ManuelW77]

Fixed #16459 Audit date is not saved when creating an asset

[what-the-diff]

PR Summary

• Enhanced Asset Updating Feature
  The updating process for 'Assets' has been improved. The date for the next audit of an asset can now be submitted and stored directly through the request. This feature will streamline the process and add convenience.

[snipe]

If the next audit date is not manually filled, it needs to be overridden by the audit rules in the notification settings. The line right below the line you added checks to see if $settings->audit_interval is empty, and if it isn't, it calculates what the next audit date will be - which means if you are trying to override the next audit date manually on the store(), the if/else right after will overwrite your intended changes.

[ManuelW77]

If the next audit date is not manually filled, it needs to be overridden by the audit rules in the notification settings. The line right below the line you added checks to see if $settings->audit_interval is empty, and if it isn't, it calculates what the next audit date will be - which means if you are trying to override the next audit date manually on the store(), the if/else right after will overwrite your intended changes.

I have different audit intervals for different devices. So as example i don't use the default interval and set the date manually. But it was not saved on creation.

[snipe]

I have different audit intervals for different devices. So as example i don't use the default interval and set the date manually. But it was not saved on creation.

That's fine, but other people do, so the order is still incorrect. If I set a specific override while generally using the interval, the audit interval math below it will overwrite that override.

[ManuelW77]

Ah, i understand what you mean. Ok, so i changed ti for respecting a filled audit interval field.