Skip loading kontact and khelpcenter on unsupported architecture

[cedvid]

• Related tickets:
  • kontact https://progress.opensuse.org/issues/159981
  • khelpcenter https://progress.opensuse.org/issues/159978
• Verification run: https://openqa.opensuse.org/tests/overview?build=cedvid%2Fos-autoinst-distri-opensuse%2319297

[github-actions]

Great PR! Please pay attention to the following items before merging:

Files matching lib/**.pm:

• Consider adding or extending unit tests in t/

Files matching t/data/test_schedule.out:

• Ensure openSUSE/SLE release managers are ok with the change in staging schedule

This is an automatically generated QA checklist based on modified files.

[foursixnine]

@cedvid, I think you need to check the default schedule but in general it shouldn´t be black magic in the end, and I think that the changes are OK, but I'm not entirely sure.

[cedvid]

@cedvid, I think you need to check the default schedule but in general it shouldn´t be black magic in the end, and I think that the changes are OK, but I'm not entirely sure.

What do you mean by default schedule? I am not sure I understand.

[foursixnine]

@cedvid, I think you need to check the default schedule but in general it shouldn´t be black magic in the end, and I think that the changes are OK, but I'm not entirely sure.

What do you mean by default schedule? I am not sure I understand.

so a default schedule is kind of whatever runs from main.pm, i.e try cloning a gnome test, and see if these modules are not shown

[cedvid]

@cedvid, I think you need to check the default schedule but in general it shouldn´t be black magic in the end, and I think that the changes are OK, but I'm not entirely sure.

What do you mean by default schedule? I am not sure I understand.

so a default schedule is kind of whatever runs from main.pm, i.e try cloning a gnome test, and see if these modules are not shown

but it wouldn't show for gnome anyway since the modules are only loaded if (kdestep_is_applicable()). Or am I misunderstanding your comment?

[foursixnine]

@cedvid to address @okurz

Or is the default scenario from a non-default architecture? Probably yes so how about excluding unsupported architectures instead of only enabling on selected architectures?

Lets make a follow, lets make a ticket to have isotovideo default scenarios for all 4 architectures, but excluding 32bits which is the root cause here.