Migrate GitRepositoryAdd to prefect

[LucasG0]

No description provided.

[codspeed-hq]

CodSpeed Performance Report

Merging #4788 will degrade performances by 18.15%

_{Comparing lgu-migrate-git-repository-add (2b969d8) with develop (fad721d)}

Summary

❌ 2 regressions
✅ 8 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	develop	lgu-migrate-git-repository-add	Change
❌	test_get_menu	421.5 ms	473.5 ms	-10.98%
❌	test_graphql_generate_schema	300.4 ms	367.1 ms	-18.15%

[ogenstad]

I would vote to enable the disabled tests related to proposed changes before merging this, i.e. these:

    @pytest.mark.xfail(reason="FIXME Works locally but it's failling in Github Actions")
    async def test_happy_pipeline(self, db: InfrahubDatabase, happy_dataset: None, client: InfrahubClient) -> None:

    @pytest.mark.xfail(reason="FIXME Works locally but it's failling in Github Actions")
    async def test_conflict_pipeline(

Then we need to figure out what's required to actually trigger the jobs to be executed in serial, so that the testing experience is somewhat similar to what we had before. In this PR we see it in the failing integration test where some more work will need to be done, but it could also be other things that are required with regards to these disabled tests. It might be that we need to rewrite them from scratch depending on the options we have with prefect. But if we look at this change:

            if context.service:
                context.service.workflow.submit_workflow(
                    workflow=GIT_REPOSITORY_ADD, parameters={"model": git_repo_add_model}
                )

We need the submit_workflow method to actually run the import repo function in the background and add the changes back to the current test instance in the same way as the old RabbitMQ message did.

[dgarros]

We need the submit_workflow method to actually run the import repo function in the background and add the changes back to the current test instance in the same way as the old RabbitMQ message did.

That should already work as expected when the tests are using WorkflowLocalExecution

[ogenstad]

That should already work as expected when the tests are using WorkflowLocalExecution

Ah, right so will just need to update that integration test. I still think it would be good to have the other tests enabled again though.