chore(ci): Force github CI for tests failing on self-hosted runners

[come-nc]

Summary

2 jobs are always failing on self hosted runners, so for now force them on github CI to avoid false-negative.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[come-nc]

smb-kerberos-sso is flaky on github CI as well, it failed 😢

[come-nc]

For php8.3-s3 it works.

[come-nc]

@susnux I see you have pushed things to docker-ci, what is your take on this, should we merge it? Or is there a better solution?

[susnux]

I see you have pushed things to docker-ci, what is your take on this, should we merge it? Or is there a better solution?

Nothing related to this. So probably we need this until someone can figure out whats up with kerberos

[susnux]

Kerberos still failing?

https://github.com/nextcloud/server/actions/runs/7712512770/job/21024244130

[come-nc]

Kerberos still failing?

nextcloud/server/actions/runs/7712512770/job/21024244130

Yes as stated above: #43210 (comment)
I do not know what is wrong with it.

[susnux]

But only for PHP8.3 I see this errors, so there might be a real issue with our code?

[nickvergessen]

But only for PHP8.3 I see this errors, so there might be a real issue with our code?

unknown, I forwarded this internally and an engineer of the team will be assigned to investigate if we can disable it safely or if a work item needs to be scheduled

[nickvergessen]

Ref #43296