Add support for commit_hash on test

[matbalc]

Add support for commit_hash, branch_tag and build_id on tests.
DefectDojo models supports these values on test level so it would be nice ddimport to allow to set these values. I have not added validation as exists on Engagement level, to threat them as optional

[StefanFl]

Hi @matbalc, thank you very much for your contribution. I would propose 2 changes, to make it even better:

• We should introduce 3 new environment variables: DD_TEST_BUILD_ID, DD_TEST_COMMIT_HASH and DD_BRANCH_TAG. Then a user can decide if they want to set the attributes in an engagement or in a test.
• The attributes should be set with an update routine after the import, like it is done for the engagement. Currently they can only be set for a new test, but not be updated in subsequent re-imports.

[matbalc]

Hi @matbalc, thank you very much for your contribution. I would propose 2 changes, to make it even better:

• We should introduce 3 new environment variables: DD_TEST_BUILD_ID, DD_TEST_COMMIT_HASH and DD_BRANCH_TAG. Then a user can decide if they want to set the attributes in an engagement or in a test.
• The attributes should be set with an update routine after the import, like it is done for the engagement. Currently they can only be set for a new test, but not be updated in subsequent re-imports.

@StefanFl good catch regarding capability to provide hash while re-uploading the test. I will adjust.
However, regarding introducing the new variables to track commit_hash for test separately from engagement is there a need for this? I can't think of scenario where I would want to set different commit hashes for engagement and for test. Could you help me to understand the need for it? Nonetheless, I don't think this is bad idea, will adjust. Just trying to think what is the actual added value in "real world scenario"

[StefanFl]

@matbalc You never know what users want to do. So in my experience it's better to be flexible and let users have the choice, if they want to set the attributes for the engagement or the tests.

[matbalc]

@StefanFl
I have updated PR to reflect your suggested changes

[StefanFl]

Hi @matbalc , thanks for the changes so far. The second part is still missing, so that the attributes can be changed in suqsequent imports, like for engagements.