More verbose logging for artifact uploading

Description

GitLab now supports multiple types of artifacts such as paths & artifact:reports:*. Inside of the job log we specify what file we are uploading for example:

Uploading artifacts...
gl-license-management-report.json: found 1 matching files 
Uploading artifacts to coordinator... ok            id=233856986 responseStatus=201 Created token=8KPxmps5

But as experienced in #4374 (closed) this can lead to confusion if the same file is set for both paths and reports for example:

job:
  artifacts:
    reports:
      license_management: gl-license-management-report.json
    paths: [gl-license-management-report.json]

Would lead to the job log below, which can lead to confusin and not very clear which type of artifact is being uploaded

gl-license-management-report.json: found 1 matching files 
Uploading artifacts to coordinator... ok            id=233856986 responseStatus=201 Created token=8KPxmps5
Uploading artifacts...
gl-license-management-report.json: found 1 matching files 
Uploading artifacts to coordinator... ok            id=233856986 responseStatus=201 Created token=8KPxmps5

Proposal

As proposed by @tmaczukin in #4374 (comment 182695875) we should had more verbose logging like:

Uploading artifacts for reports:license_management...
gl-dependency-scanning-report.json: found 1 matching files
Uploading artifacts to coordinator... ok            id=233504430 responseStatus=201 Created token=nT3zboF9
Uploading artifacts for reports:junit...
junit.xml: found 1 matching files
Uploading artifacts to coordinator... ok            id=233504430 responseStatus=201 Created token=nT3zboF9
Uploading artifacts for defined paths...
gl-dependency-scanning-report.json: found 1 matching files
junit.xml: found 1 matching files
Uploading artifacts to coordinator... ok            id=233504430 responseStatus=201 Created token=nT3zboF9

Links to related issues and merge requests / references

#4374 (closed)