Update add-ons test to have common-dev dependencies as a part of tgz upload

[mukulpalit-ibm]

Currently the add-ons test is failing in projects which is triggering an ansible pipeline in automation as the common dependency files are not available in the upload

 2025/09/19 11:33:44 Related Action: actionID=us-east.ACTION.7f0016a7-b7d7-4306-b3b4-46015aa09802-validate-pre-script.97dca31c
 2025/09/19 11:33:56  --- Ready to execute the AnsibleV2TemplateCmd command --- 
 2025/09/19 11:33:58 [1m[31mSchematics sandbox action failure while downloading the repo / repo SHA validation. Check the log message for the failure details[39m[0m
 2025/09/19 11:33:58 Retrying the action.
 2025/09/19 11:34:03  --- Ready to execute the AnsibleV2TemplateCmd command --- 
 2025/09/19 11:34:05 [1m[31mSchematics sandbox action failure while downloading the repo / repo SHA validation. Check the log message for the failure details[39m[0m
 2025/09/19 11:34:05 Retrying the action.
 2025/09/19 11:34:10  --- Ready to execute the AnsibleV2TemplateCmd command --- 
 2025/09/19 11:34:13 [1m[31mSchematics sandbox action failure while downloading the repo / repo SHA validation. Check the log message for the failure details[39m[0m
 2025/09/19 11:34:13 Retrying the action.
 2025/09/19 11:34:18  --- Ready to execute the AnsibleV2TemplateCmd command --- 
 2025/09/19 11:34:28 [1m[31mSchematics sandbox action failure while downloading the repo / repo SHA validation. Check the log message for the failure details[39m[0m

[ocofaigh]

There is a known issue with Schematics where this error occurs. The root cause is that there are broken symlinks in the code. As a workaround in the catalog pipeline we actually initialise the git submodule, generate a new tgz file with the git submodule files in it (so symlinks work) and import the tgz file to catalog.

Its not so easy for add-ons tests though because there is no uploaded tgz. The test imports the git branch directly to catalog. We need to find a way to handle this in the add-ons tests