RTC Test Additions

[RichardSWheatley]

Current RTC testing for alarm includes only hour and minute.
Some RTCs do not allow such alarms and require more configs.

This Issue was formed from discussion below where the consensus was to have test coverage for RTC Full Config Alarm and for Partial Config Alarm (may or not be the ending names for the tests).

Discussed in #72480

^{Originally posted by RichardSWheatley May 8, 2024}
Hello, @bjarki-trackunit!

You are the maintainer for the RTC section.
I am writing the Ambiq RTC driver when I noticed that the tests for RTC make some assumptions that are not true for the Ambiq RTC.

1. We do not support 99-00 rollover which I already fixed in the tests by adding a check for EINVAL.

	if (ret == -EINVAL) {
		TC_PRINT("Rollover not supported\n");
		ztest_test_skip();
	} else {
		zassert_ok(ret, "RTC Set Time Failed");
	}

2. When setting the alarms, for the Ambiq RTC you must set the entire struct with a non-zero value

This makes our implementation fail the most of the testing without additions to the tests.
I do not like to make additions to tests unless it is absolutely needed.

Do you think there is a better way to accomplish this?

[RichardSWheatley]

@bjarki-trackunit I have started the work but have gotten busy at my job.
I am commenting here so that this won't be marked stale.

[bjarki-trackunit]

Don't worry, the stale bot waits for 60 days :) also, I'm invested in the addition so if you don't have time I will gladly add it :)

[RichardSWheatley]

Don't worry, the stale bot waits for 60 days :) also, I'm invested in the addition so if you don't have time I will gladly add it :)

I'm going to be honest, I do not have the time since my company is putting out new software releases monthly.

[bjarki-trackunit]

Noted, I will find time to do it :)