tests: drivers: spi: spi_loopback: Update slow rates for MAX32 boards

The requested SPI clock rate and the actual rate that is set can be
different depending on the peripheral clock and divisors available to
the SPI peripheral. For some MAX32 SoCs, actual rate ended up being
higher than the devicetree setting. This would then cause latency tests
to fail as transfers finish earlier than minimum expected duration.

Update the test frequency values in several MAX32 board overlays to pass
latency tests.

Signed-off-by: Tahsin Mutlugun <Tahsin.Mutlugun@analog.com>

Author: ttmut

tests/drivers/spi/spi_loopback/boards/max32666fthr_max32666_cpu0.overlay

@@ -11,7 +11,7 @@
 	slow@0 {
 		compatible = "test-spi-loopback-slow";
 		reg = <0>;
-		spi-max-frequency = <128000>;
+		spi-max-frequency = <150000>;
 	};
 	fast@0 {
 		compatible = "test-spi-loopback-fast";

tests/drivers/spi/spi_loopback/boards/max32675evkit.overlay

@@ -11,7 +11,7 @@
 	slow@0 {
 		compatible = "test-spi-loopback-slow";
 		reg = <0>;
-		spi-max-frequency = <128000>;
+		spi-max-frequency = <125000>;
 	};
 	fast@0 {
 		compatible = "test-spi-loopback-fast";

tests/drivers/spi/spi_loopback/boards/max32690evkit_max32690_m4.overlay

@@ -11,7 +11,7 @@
 	slow@0 {
 		compatible = "test-spi-loopback-slow";
 		reg = <0>;
-		spi-max-frequency = <128000>;
+		spi-max-frequency = <125000>;
 	};
 	fast@0 {
 		compatible = "test-spi-loopback-fast";

tests/drivers/spi/spi_loopback/boards/max78002evkit_max78002_m4.overlay

@@ -11,7 +11,7 @@
 	slow@0 {
 		compatible = "test-spi-loopback-slow";
 		reg = <0>;
-		spi-max-frequency = <128000>;
+		spi-max-frequency = <125000>;
 	};
 	fast@0 {
 		compatible = "test-spi-loopback-fast";