Server audit must generate CUID during entity creation and not during audit flush

This should improve the ordering of the resulting audit entries, (if front-end would sort the results by CUID and not by timestamp).
For example - it would me more logical to the user if he sees that triggers on the host would be generated AFTER the generation of the host. Currently, host and trigger audit entities are mangled inside the hashset and get inserted into DB in essentially the random order. We currently generate CUID in the order we send data into DB. If we would generate CUID when we generate audit entities - this could in theory improve the ordering.