[Test] Adapt Podman tests to airgap disconnected cluster

[martinszuc]

What does this PR do?

BuildPushRunPodmanContainerAPI & KubedockPodmanTest now use dockerfile-hello-world from internal and public github repositories available on airgap & online clusters.
Solution:

• Created a mirror of the dockerfile-hello-world repository on the internal GitHub accessible in air-gapped environments at https://gh.crw-qe.com/test-automation-only/dockerfile-hello-world
• Added new environment variable TS_SELENIUM_AIRGAP_FACTORY_GIT_REPO_URL to specify Git repository URL for disconnected environments
• Modified both test classes to dynamically select the appropriate repository URL based on cluster connectivity

Successful test runs:
online:

• Build #35305: BuildPushRunPodmanContainerAPI | (OCP 4.18 on PSI) (Apr 10, 2025, 3:28:02 PM)
  
• Build #35308: KubedockPodmanTest | (OCP 4.18 on PSI) (Apr 10, 2025, 3:34:09 PM)
  

airgap:

• Build #35307: KubedockPodmanTest | (OCP 4.15 on PSI) (Apr 10, 2025, 3:34:03 PM)
  
• Build #35306: BuildPushRunPodmanContainerAPI | (OCP 4.15 on PSI) (Apr 10, 2025, 3:28:10 PM)
  

Screenshot/screencast of this PR

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-8365

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix or new feature
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[SkorikSergey]

Looks good for me.

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (1)

tests/e2e/specs/api/BuildPushRunPodmanContainerAPI.spec.ts:51

• Ensure that the file Dockerfile.${ARCH} exists in the $PROJECT_SOURCE directory, as the previous auto-generated Dockerfile creation has been removed. Adding a check or a clear comment on the expected source of this file could help avoid build failures.

podman build -t "${IMG}" -f Dockerfile.${ARCH} .

[dmytro-ndp]

@martinszuc : the suggesting which Copilot made in his comment above sounds reasonable, IMHO.

Would you, please, include a verification step for the presence of the Dockerfile in the project, with a meaningful error message?

[martinszuc]

@martinszuc : the suggesting which Copilot made in his comment above sounds reasonable, IMHO.

Would you, please, include a verification step for the presence of the Dockerfile in the project, with a meaningful error message?

Actually useful review! Copilot found that step - Check the project files were imported was missing in BuildPushRunPodmanAPI test

	test('Check the project files were imported', async function (): Promise<void> {
		const projectSection: ViewSection = await projectAndFileTests.getProjectViewSession();
		expect(await projectAndFileTests.getProjectTreeItem(projectSection, 'Dockerfile.x86_64'), 'Dockerfile not found in the project tree').not.undefined;
	});

added it into test suite setup

[dmytro-ndp]

looks good to merge