Distinguish Evergreen artifacts links across restarts for testing tasks

In a recent patch build with a task restart, both task executions managed to generate and upload the artifacts tarball. However, the artifacts tarball of the older execution was overwritten by the newer execution (by comparing the artifacts file names), which is undesired. 

Need to find a way to distinguish the artifacts tarball names for task executions.