fix(PeriphDrivers): MSDK-1287: Fix MAX32655 MXC_Delay on RISC-V shows different behavior when not compiling with -O0

[dnguye14-adi]

Description

In the MSDK Dual Core Sync example for MAX32655, the LED was programed to turn on in 500ms and then turn off.
Issue: when compiling with -O0, the LED stayed on for 500ms correctly. But, when compiling with -O1, -O2, -Os and -Og, the LED stayed on for longer (around 33% longer than the expected one).
To reproduce, just compile the example changing the MXC_OPTIMIZE_CFLAGS accordingly.

Fix: Add a delay to prevent the CPU bothers PCCR too much, then the PCCR hardware can maintain the correct timing.

Checklist Before Requesting Review

• PR Title follows correct guidelines.
• Description of changes and all other relevant information.
• (Optional) Link any related GitHub issues using a keyword
• (Optional) Provide info on any relevant functional testing/validation. For API changes or significant features, this is not optional.

---

[ttmut]

Why 3?

[dnguye14-adi]

It need a delay here to prevent CPU bother PCCR too much, then causes PCCR hardware cannot maintain the correct timing. After some testing I found this divisor (/3), it will give a delay less than 1us and big enough to prevent the PCCR. Here are my signal after add this delay, for both -O0, -O2 and -Og: