Optimize table section reloads after closing an unsaved modal

[blesildaramirez]

Details of the changes:

• In some areas, we directly call triggerDataChange(). Passing an empty param to the triggerDataChange() function will always trigger all the callbacks. Example where we use this is when Uploading Files, where there are multiple ajax legacy modals steps that only pass the dataChanged at the last step. Skipping midway prevents the reload of the files, so we need to always ensure that opening File Uploads always refreshes the list. Adding new Galley also opens the File Uploads in the process, so this one also requires this approach.
• Some other sections in our app doesn't use triggerDataChange api and manually refetches some list, so manual checks were added: shouldTriggerDataChange(closeData)
• Removed bunch of wrapper functions when calling triggerDataChange, so all params sent to it will propagate directly to triggerDataChange api.
• Closing a side modal now closes the modal first, then shows a full-screen freeze overlay while the table reloads behind it. The overlay clears as soon as the reload finishes. The freeze only shows when a reload will actually run. Modals that closes without reloads (like a plain Cancel) show no screen freeze overlay.
• We made onClose awaitable so the freeze stays up until the reload is complete.

[jardakotesovec]

Lets discuss this further on catch up. One of the goals I think was to reload the data before closing the modal, which per my testing is not happening (tried it on the task template manager).
Otherwise conceptually I think its good idea.

[jardakotesovec]

should be used the modalLevel which is available above?

Might not make difference but dialogLevel was made intentionally to guide dialogs on which levels to show up.