arch/xtensa: fix definition for _int32_t and _uint32_t

[fdcavalcanti]

Summary

Modify types.h and inttypes.h to use the correct _int32_t and _uint32_t types, on Xtensa arch.

This PR solves an issue first mentioned in #15755.

Type is now defined according to recent compiler versions.

On xtensa-esp32-gcc version 8.4.0 we have:

#define __INT32_TYPE__ int
#define __UINT32_TYPE__ unsigned int

While version 12.2.0 has:

#define __INT32_TYPE__ long int
#define __UINT32_TYPE__ long unsigned int

Due to this type modification, many logging calls had to be fixed with the proper format specifiers: %u, %lu, %ld, etc across arch and board files.

Impact

• Impact on user: No.
• Impact on build: Yes, but all fixes are present in this PR.
• Impact on hardware: Yes, Xtensa devices only.
• Impact on documentation: No.
• Impact on security: No.
• Impact on compatibility: Yes, improves compatibility since it uses the proper int types as specified by the compiler.

Testing

Most tests done on Espressif's internal CI. Each build that failed had the error fixed, resulting in the commits of this PR.
Since errors are all logging related, the build system should catch everything.

Tested build on all defconfigs for:

• esp32-devkitc
• esp32-ethernet-kit
• esp32-lyrat
• esp32-pico-kit
• esp32-wrover-kit
• esp32s2-saola-1
• esp32s3-devkit
• esp32s3-korvo-2
• esp32s3-lcd-ev

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR appears to meet the NuttX requirements. The summary clearly explains the problem, the solution, and the affected code. The impact section addresses all relevant areas, noting the specific hardware affected (Xtensa) and the improved compatibility. While ideally more detailed local testing logs would be included, the explanation regarding Espressif's internal CI and the comprehensive list of tested defconfigs provide reasonable assurance of testing. The connection to issue #15755 adds valuable context.

[xiaoxiang781216]

Due to this type modification, many logging calls had to be fixed with the proper format specifiers: %u, %lu, %ld, etc across arch and board files.
No, you should use PRIxyy from include/inttypes.h to be portable.

[fdcavalcanti]

@yamt seems we have an issue on toywasm. Could you please take a look at the CI build log?

[fdcavalcanti]

Applied the changes recommended. Let's please hold this PR while we fix the toywasm build.