compiler warning when i3c device and CONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU=y

[mertekren]

Describe the bug

Following compiler warning occurs when I3C device with 9 byte of reg address to dts, and DCONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU=y.
C:/repos/ADI-zephyr/zephyr/arch/arm/core/mpu/arm_mpu.c: In function 'z_arm_mpu_init':
C:/repos/ADI-zephyr/zephyr/arch/arm/core/mpu/arm_mpu.c:481:8: warning: integer constant is too large for its type
481 | (!DT_NULL_PAGE_DETECT_NODE_EXIST)

• I3C device requires 9 byte of address according to i3c-device.yaml
  https://git.byronlathi.com/bslathi19/zephyr/-/blob/main/dts/bindings/i3c/i3c-device.yaml?ref_type=heads

To Reproduce

1. Build a board with M33 with DCONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU=y with a tests/*:
   example:
   west build -b mimxrt685_evk/mimxrt685s/cm33 .\tests\drivers\uart\uart_basic_api\ -p always -DCONFIG_NULL_POINTER_EXCEPTION_DETECTION_MPU=y
2. See the compiler warning:
   warning: integer constant is too large for its type
   481 | (!DT_NULL_PAGE_DETECT_NODE_EXIST)

Expected behavior

Compiler warning shall not occur.
Impact

CI/CD requires -Werror option, thus this fails CI/CD procedure in out-of-tree zephyr pipeline.
Logs and console output

Environment (please complete the following information):

• Zephyr 4.00+ (macro DT_NULL_PAGE_DETECT_NODE_EXIST added here )
• OS: all
• Toolchain Zephyr SDK
• Commit SHA or Version used

[github-actions]

Hi @mertekren! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙