Clarify cicd.pipeline.task.run.id uniqueness

[kamphaus]

Fixes #3566

Changes

Clarify that cicd.pipeline.task.run.id must be unique within a pipeline run
and that this id may be used for correlating results of a task across several pipeline runs.

Important

Pull requests acceptance are subject to the triage process as described in Issue and PR Triage Management.
PRs that do not follow the guidance above, may be automatically rejected and closed.

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• Change log entry added, according to the guidelines in When to add a changelog entry.
  • If your PR does not need a change log, start the PR title with [chore]
• Links to the prototypes or existing instrumentations (when adding or changing conventions) → NA

[github-actions]

This PR has been labeled as stale due to lack of activity. It will be automatically closed if there is no further activity over the next 7 days.

[joaopgrassi]

Suggested change

	For a given pipeline run and task the `cicd.pipeline.task.run.id` MUST be unique.
	For different pipeline runs of the same pipeline the task run id MAY remain the same and thus MAY allow correlating the `cicd.pipeline.task.run.result`
	For a given pipeline run and task, the `cicd.pipeline.task.run.id` MUST be unique.
	For different runs of the same pipeline, `cicd.pipeline.task.run.id` MAY remain the same and allow correlating with `cicd.pipeline.task.run.result`

I got confused with the multiple "pipeline and pipeline runs" so I rephrased it a bit. Also, I'm not entirely sure about the "correlation" part. Do we really need to include that? I don't particularly get any helpful insight from it from the small text here. Consider either removing it or maybe adding more explanation on how it can be correlated?