logging: Increase log processing stack size when NO_OPTIMIZATIONS
logging: Increase log processing stack size when NO_OPTIMIZATIONS

When optimizations are disabled more RAM is used and we get a stack
overflow on CONFIG_LOG_PROCESS_THREAD_STACK_SIZE. To rectify this,
increase the stack size when CONFIG_NO_OPTIMIZATIONS.

This does not scale well, and will have to be replaced by a a more
general solution eventually, but in the mean time it follows the
existing best practice established by the GCOV infrastructure in
commit e908ea9aa51ba7f88dff7dd610076b4dc352d3cf

Signed-off-by: Sebastian Bøe <edee888afd63e94916688495334700803eba20a0@nordicsemi.no>

nashif/zephyr,explora26/zephyr,galak/zephyr,finikorg/zephyr,finikorg/zephyr,Vudentz/zephyr,GiulianoFranchetto/zephyr,ldts/zephyr,explora26/zephyr,galak/zephyr,finikorg/zephyr,ldts/zephyr,zephyrproject-rtos/zephyr,ldts/zephyr,ldts/zephyr,GiulianoFranchetto/zephyr,zephyrproject-rtos/zephyr,GiulianoFranchetto/zephyr,zephyrproject-rtos/zephyr,nashif/zephyr,ldts/zephyr,galak/zephyr,Vudentz/zephyr,GiulianoFranchetto/zephyr,zephyrproject-rtos/zephyr,explora26/zephyr,Vudentz/zephyr,zephyrproject-rtos/zephyr,nashif/zephyr,explora26/zephyr,finikorg/zephyr,galak/zephyr,nashif/zephyr,Vudentz/zephyr,Vudentz/zephyr,nashif/zephyr,Vudentz/zephyr,galak/zephyr,GiulianoFranchetto/zephyr,explora26/zephyr,finikorg/zephyr