test: app_development: vector_table_relocation: exclude stm32f4 serie

The vector_table_relocation.dtcm test assumes that the vector
table can be relocated to a DTCM region and executed from there.
However, on STM32F4 (Cortex-M4),this is not possible due to
architectural constraints.
The CCM RAM on STM32F4 series is connected via the D-bus,
not the ICode bus, and therefore cannot serve as an executable boot
space for the vector table.

Signed-off-by: Fabrice DJIATSA <fabrice.djiatsa-ext@st.com>

tests/application_development/vector_table_relocation/testcase.yaml

@@ -14,7 +14,11 @@ tests:
 
   application_development.vector_table_relocation.dtcm:
     arch_allow: arm
+    # Exclude STM32F4 series due to architectural constraints. STM32F4 CCM is only accessible
+    # over the D-bus but exception vectors are fetched over the I-bus.
+    # As such, the vector table can't be relocated to CCM.
     filter: CONFIG_CPU_CORTEX_M_HAS_VTOR and dt_chosen_enabled("zephyr,dtcm")
+            and not CONFIG_SOC_SERIES_STM32F4X
     extra_configs:
       - CONFIG_ARM_VECTOR_TABLE_DTCM=y