Reduce file events arguments

Events that include files information in their arguments tend to have many arguments (`sched_process_exec` is the extreme example for it).
To reduce the amount of arguments and make it more user friendly, I propose to create a `FileInfo` struct to contain the data that is always passed by events on files - path, device, inode and ctime.
This change will probably break many rules for our users, but will improve the accessibility for new users.
WDYT?

No files or tests are named. Start by locating the definitions for file-related event arguments, including sched_process_exec, and identify the rules that consume path, device, inode, and ctime. Done means those shared values are represented by a FileInfo struct and the affected user-facing rules continue to work with the changed arguments.

Written by the indexing model from the issue text.