Create test resources for go library and avoid using external repos

[thepetk]

Which area this feature is related to?

/area test

Issue details

There are files like git_test.json that are providing external repos as test resources. This makes alizer's test depend to the status of those repos. We should use mocked or test resources instead of this, in order to be sure that our test have always the same resources

Target date: 11 May 2023

[thepetk]

Update: Working on a PR that will include all those external repos inside the code and avoid cloning those projects every time a build is run.

[thepetk]

I've been working on 2 workarounds:

1. Import all repos mentioned inside git_test.json inside this repository and replace github URL to local dir path (plus some updates in the git_test functionality). The issue here is that the alizer repo will become huge after this update as a lot of new files must be created.
2. We can create a new repo which will be inside devfiles team and add every repo mentioned inside git_test.json to this repo as a directory. This way again we will have to clone from git in order to perform testing. As a plus, we do not need to make changes except than updating the git_test.json

[thepetk]

Update: I've created the https://github.com/devfile-resources/alizer-test-resources repo in order to import there all test resources of Alizer. I've added them all in this PR

[thepetk]

Update: The alizer test resources repo is fully updated and the PR is now ready for review