Schedule nginx test in ci

[asdil12]

No description provided.

[Martchus]

I was just asking for splitting into multiple commits, not a separate PR. However, this is ok as well.

[okurz]

I suggest you also manually trigger openQA tests based on that new schedule definition to verify

[asdil12]

Looks good. Tested on local instance due to the O3 migration being in progress right now.
This (unavailable repos via o3) is also the reason why this job failed later.

[okurz]

why do we need this setting?

[asdil12]

idk - I copied the section above which has the same setting.
@baierjan I guess you added that section. Any special reason for this line?

[baierjan]

If I recall correctly, the default https protocol failed in some step (maybe due to the weird proxy setup on o3?), this was a workaround recommended by @okurz (https://suse.slack.com/archives/C02AJ1E568M/p1682587547710399?thread_ts=1682587184.320269&cid=C02AJ1E568M)

[okurz]

Well, that proxy setup is over. Let's try without this setting :) @asdil12 can you please remove it in another commit from all mentions in this file

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏

[kalikiana]

@Mergifyio rebase

[mergify]

rebase

❌ Base branch update has failed

Git reported the following error:

Rebasing (1/1)
Auto-merging scenario-definitions.yaml
CONFLICT (content): Merge conflict in scenario-definitions.yaml
error: could not apply 95cbb8d... Schedule nginx test in ci
hint: Resolve all conflicts manually, mark them as resolved with
hint: "git add/rm <conflicted_files>", then run "git rebase --continue".
hint: You can instead skip this commit: run "git rebase --skip".
hint: To abort and get back to the state before "git rebase", run "git rebase --abort".
Could not apply 95cbb8d... Schedule nginx test in ci

err-code: 002FA