In #5017 it was discussed how we lacked a ztest for certain functionality because it's difficult to cover with ztest, and in an offline discussion with @nwt he confirmed this boils down to the fact that a robust ztest would be fairly slow to run (e.g., requires conservative sleep timers). This reminded @nwt that he's got other slower tests that he'd prefer to tag & run separately, perhaps primarily in CI, e.g., the Python tests. This would still give us adequate coverage but without slowing down developers who need to frequently run the majority of our tests locally.

@nwt indicated most of the mechanisms are in place to allow for this but he'd need to add a couple things to tie it all together, so this is just a reminder to make sure we do that and add a test for what's in #5017 as part of that.