Feature/add versioning

[mikemcd3912]

Issue #, if available:
#125

Description of changes:
Added label to the README for new labeling requirements
Updated partner Namespace files with the current versions based on available Helm chart versions
Updated Validated Partner files for each environment with the Version field and associated values

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[mikemcd3912]

GH Action failed because I updated the Validated Partners files outside of the normal reporting workflow, and is expected behavior

[elamaran11]

@mikemcd3912 Nice work, couple of comments. We should use Automation to update the Partner list with Versions. We should not update manually. And Reason why manifestJob was removed.

[mikemcd3912]

I pulled ManifestJob because it seemed like it was associated with testing and therefore would serve as a distraction from our current examples for ChronJobs in the Testers folder. Updated PR to remove that deletion only modify Version update files

[elamaran11]

I pulled ManifestJob because it seemed like it was associated with testing and therefore would serve as a distraction from our current examples for ChronJobs in the Testers folder. Updated PR to remove that deletion only modify Version update files

It is a sample. I think our ReadMe references this if im not mistaken. Lets keep it as a source of sample to share to partners who ask. This helps us being not biased to share any particular partner sample to anyone!

[elamaran11]

LG

[elamaran11]

Looks like your deployment dynatrace-dynatrace-operator is failing.
Specifically, it looks like these pods are failing:

• Pod: dynatrace-dynatrace-operator-6859dbbd89-7n2sx.

---