xtensa: Disable interrupts on entry to _Cstart
xtensa: Disable interrupts on entry to _Cstart

Zephyr isn't ready to handle interrupts yet, until the
threading/scheduler are set up and we make our first context switch.
This was a semi-hidden bug: only the timer interrupt would actually
get unmasked before the system was ready, and obviously would never
have time to fire a tick before the system completed initialization.
But a combination of system load and a new version of Qemu (which
seems to be more sensitive to non-deterministic timing glitchery) has
made this visible.  About 2-3% of the time when run under a full
sanitycheck, the qemu process will get swapped away for long enough
that the tick timer expires before _Cstart() has reached
enable_multithreading().

It looks like the original code was cut and pasted from another
implementation, which was expected to call into an "application"
main() routine that wanted interrupts ready.

Fixes #11182

(Note also that this code is not used for ESP-32, which has its own
startup path)

Signed-off-by: Andy Ross <c70f9a6bf6ee0cd69c8af4ce5e6b131945769315@intel.com>

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