logging: frontends: stmesp: Add turbo logs

[nordic-krch]

Add 'turbo' logging feature. When enabled, short logs (no argument or one numeric, 32 bit argument) are handled in a special way that is much faster than the default one (>10x faster). Additionally, there is an option to remove all other logs from the system which allows to not include almost any logging framework code in the binary (~170 bytes of code is needed). It may be especially valuable for memory constraint targets (ppr, flpr) where with only 170 byte of code (+code for each log message) we can provide limited formatted string logging support.

'Turbo' logging is using following tricks to achieve that:

• logging strings are put into a memory section and additional memory section is created which holds addresses of those strings. Index in that array is used to identify a string (32 bit address is encoded into a smaller number, 15 bits is more than enough). This index is used for a STMESP register set (there are 2^16 available). STMESP channel encodes string.
• Logging level is stringified and prepended to a string
• Source ID is encoded by using DM16 (so far not used).
• Log without arguments is written as DMTS16
• Log with one argumetn is written as DM16+DMTS32

samples/boards/nordic/coresight_stm
Without turbo logs:

flpr: Timing for log message with 0 arguments: 1.20us
flpr: Timing for log message with 1 argument: 2.20us
flpr: Timing for log message with 2 arguments: 1.80us
flpr: Timing for log message with 3 arguments: 2.30us
flpr: Timing for log_message with string: 3.80us
flpr: Timing for tracepoint: 0.10us
flpr: Timing for tracepoint_d32: 0.10us
app: Timing for log message with 0 arguments: 1.80us
app: Timing for log message with 1 argument: 1.90us
app: Timing for log message with 2 arguments: 2.0us
app: Timing for log message with 3 arguments: 2.10us
app: Timing for log_message with string: 4.40us
app: Timing for tracepoint: 0.5us
app: Timing for tracepoint_d32: 0.10us
ppr: Timing for log message with 0 arguments: 25.40us
ppr: Timing for log message with 1 argument: 27.20us
ppr: Timing for log message with 2 arguments: 27.70us
ppr: Timing for log message with 3 arguments: 27.60us
ppr: Timing for log_message with string: 65.50us
ppr: Timing for tracepoint: 0.65us
ppr: Timing for tracepoint_d32: 0.30us

and with turbo logs:

flpr: Timing for log message with 0 arguments: 0.10us
flpr: Timing for log message with 1 argument: 0.20us
flpr: Timing for log message with 2 arguments: 2.20us
flpr: Timing for log message with 3 arguments: 2.20us
flpr: Timing for log_message with string: 3.90us
flpr: Timing for tracepoint: 0.0us
flpr: Timing for tracepoint_d32: 0.10us
app: Timing for log message with 0 arguments: 0.10us
app: Timing for log message with 1 argument: 0.20us
app: Timing for log message with 2 arguments: 2.10us
app: Timing for log message with 3 arguments: 2.0us
app: Timing for log_message with string: 4.60us
app: Timing for tracepoint: 0.5us
app: Timing for tracepoint_d32: 0.5us
ppr: Timing for log message with 0 arguments: 2.10us
ppr: Timing for log message with 1 argument: 3.10us
ppr: Timing for log message with 2 arguments: 27.80us
ppr: Timing for log message with 3 arguments: 27.40us
ppr: Timing for log_message with string: 68.20us
ppr: Timing for tracepoint: 0.55us
ppr: Timing for tracepoint_d32: 0.30us

It is based on #79419 and #79420.

[nordic-krch]

@nordic-segl fyi. If that goes in then test for coresight_stm will need to be updated with new timings.