move some git integration test setup into the test

[s-hertel]

SUMMARY

Add a simple, unauthenticated git server for git tests that can't easily use the local protocol and replace a few external Github dependencies.

This should make it easier to add new tests for submodules, needed by #80456, and any bugfix for #83146.

Related #82013

ISSUE TYPE

• Test Pull Request

[webknjaz]

that can't easily use the local protocol

Could you expand on what this means? Is there a case where pointing a git remote to an fs-local .git folder path doesn't work?

[webknjaz]

Can this be done through a .gitmodules file instead?

[s-hertel]

This does create .gitmodules.

[webknjaz]

Usually, doing the following works just fine:

-          - 'git submodule add --name submodule1 git://localhost/test_submodules_subm1.git submodule1'
+          - 'git submodule add --name submodule1 file://path/to/bare/repo/test_submodules_subm1.git submodule1'

Or maybe

-          - 'git submodule add --name submodule1 git://localhost/test_submodules_subm1.git submodule1'
+          - 'git submodule add --name submodule1 ../relative/path/to/bare/repo/test_submodules_subm1.git submodule1'

(I don't remember which one works better, but I did use this in the past)

[s-hertel]

The goal of this PR is to replace dependencies on external Github repos that aren't managed by Ansible, and not be limited to 1 protocol since some features cannot be tested with file://.

The current tests use absolute URLs, so that's why these are absolute. I could use file:// for these specifically, but a git server is necessary to fully test relative submodules (which can be relative to the repo or origin remote), and because I know that submodules relative to the remote are broken (see #83146), I added the git daemon in this PR to make sure it works with our existing test cases, before I add more complex submodule tests.

[webknjaz]

Ah, I see. Thanks for explaining!

[s-hertel]

I need to fix this change so the same error can occur for every retry attempt (it's difficult to spot the real cause of the test failure - https://dev.azure.com/ansible/ansible/_build/results?buildId=142962&view=logs&j=5e252db1-1db5-5540-3a64-4369eb0bd6ec&t=f64c9d35-7d74-5543-3054-69a140aa75b8&l=2377). #85015 fixes the cause of the test failure and fixes resetting between retry attempts.

[webknjaz]

I'm re-adding ci_verified since you've confirmed earlier that this PR causes the problem, even if indirectly. So I think it should remain excluded from the CI maintenance queue.

[s-hertel]

Makes sense. Since this is just a POC anyway, I moved it out of the CI workflow for now.