core/arm32: add traces in case of user TA abort

TA manager and TA mmu layer have specific trace handlers for TA aborts:
- dumping TA info.
- dumping TA mapping info.

Core log level displays physical memory and core information.
TA log level displays only TA virtual space information. Core log
level can display some teecore private information (i.e physical
addresses, TA manager structures, ...).

Generic helper tee_uuid2str().

Reviewed-by: Pascal BRAND <pascal.brand@st.com>
Reviewed-by: Etienne CARRIERE <etienne.carriere@st.com>
Tested-by: Etienne CARRIERE <etienne.carriere@st.com>
Signed-off-by: Pascal Brand <pascal.brand@st.com>
I find the use of TAMSG_RAW vs. EMSG_RAW confusing since in the end it is the same thing. Same for the comment about "TA log level": what is it? There is CFG_TEE_CORE_LOG_LEVEL which controls traces in kernel code, i.e. currently affects both EMSG_RAW and TAMSG_RAW. Then there is CFG_TEE_TA_LOG_LEVEL, which is irrelevant here because it controls code that is compiled for user mode. Well that is my understanding.
So, to make things less confusing, I would suggest two options:
1. Either make TAMSG_RAW insert a prefix to show that it's a message from the TEE Core, but related to a TA. This would justify the use of two macros.
2. Or drop TAMSG_RAW and use EMSG_RAW everywhere instead.