projects: adalm-lsmspg: Add support for max32655fthr

[thorenscientific]

Both tinyiiod and curvetrace_examples.

Pull Request Description

Add support for the MAX32655FTHR , typically used in no-OS hands-on workshops.

PR Type

• Bug fix (change that fixes an issue)
• New feature (change that adds new functionality)
• Breaking change (has dependencies in other repos or will cause CI to fail)

PR Checklist

• I have followed the Coding style guidelines
• I have complied with the Submission Checklist
• I have performed a self-review of the changes
• I have commented my code, at least hard-to-understand parts
• I have build all projects affected by the changes in this PR
• I have tested in hardware affected projects, at the relevant boards
• I have signed off all commits from this PR
• I have updated the documentation (wiki pages, ReadMe etc), if applies

[thorenscientific]

@nacuna-adi can you take a peek at this? I started with your original MAX32665 target and "vibe coded" in support for MAX32655. There were quite a few subtleties - CS selection, and getting the heartbeat timer to initialize properly. Surprisingly the acual UART (as opposed to the MAX32666's USB UART) worked pretty much the first time. I've tested out all four builds - IIO/standalone curve tracer on both boards and they look good, but would be great to get confirmation from you as well.

@amiclaus your input always appreciated, and I believe you reviewed Neil's original project. Can you take a look at this for style, correctness, etc., and that it's set up to generate four configurations in the release - iio and curvetrace_example for each target board? One concern is the MSDK version - I believe there is still a bug with the I2C driver in the latest release, we had to use the June 2023 release for this. Which version is used for building Maxim targets here?

If it doesn't look too terrible I'll de-draft the PR. Thanks!