ALP: create new product "alp" with its main.pm

[jlausuch]

This ALP PoC in openQA can have its own product directory,
similar to microos, leap-micro or sle-micro.
For these jobs, we will be using DISTRI=alp, which means
new way of scheduling tests.
I am proposing to create this main.pm which will be the main
entry point for scheduling tests for ALP. Most of them are
the same as for MicroOS/Leap-Micro, and I might come up with
a common schedule file file for ALL these transactional-server
based products, but for now, I would prefer to keep it with
single main schedule.

Related ticket: https://progress.opensuse.org/issues/112409

[foursixnine]

I would shy away from using the old style of scheduling tests, but if you're already having the thought on your mind, then I have no objections :)

[jlausuch]

I would shy away from using the old style of scheduling tests, but if you're already having the thought on your mind, then I have no objections :)

It's a long story :)
We have seen a lot of limitations using yaml schedule, specially with conditions, and specially in containers area. For that reason we created main_containers.pm and main_publiccloud.pm which can handle complex conditions. In MicroOS family case we have actually 4 products that will share kind of schedule: MicroOS, Leap-Micro, SLE-Micro and now ALP. And currently, there is some mess in the way the tests are scheduled, e.g. SLE Micro and Leap Micro use yaml schedule, MicroOS uses another schedule. My vision is that I will like to combine all those schedules into single place (main_transactional.pm?), but I will need some time for that :) So, let's just keep it as it's and let me work on a clean solution for all those products which have common tests later on.