trace: secure_buffer: Introduce trace events for secure buffer

These trace events will show the caller of hyp_assign_table() as well as
information about the region(s) of memory that are affected by the changes
in ownership (e.g.  source/destination VMIDs and permissions). The trace
events also provide information about the time spent in the higher
execution layers when the memory is being assigned.

Also, expose the mem_prot_info and dest_vm_and_perm_info data structures in
the secure_buffer header file, so that they are visible to the trace events
header file.

Change-Id: I19a8561327e953e1bc593217293642f1cbd6ce36
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Signed-off-by: Chris Goldsworthy <cgoldswo@codeaurora.org>