Fix lifecycle-status logging feature | charts-build-scripts automation related

[nicholasSUSE]

Scope

Repository to work on: charts-build-scripts repo Repository affected by automation: charts repo

The lifecycle-status feature is responsible for doing several comparisons to aid in the release of charts. One of these comparisons is:

• Get all asset versions in the official development branch
• Get all asset versions in the official production branch
• Compare which charts are present on dev but not present on production but should be.

These asset versions we call as charts to be forward-ported.

Within this comparison are coming some asset versions named with:

• x.y.z+upx.y.z`-RC`
• x.y.z+upx.y.z`-rancher1`

These "-rc" and/or "-rancher1" versions are used for testing. They should not be forward-ported.

This bug was seen after executing the implementation of make auto-forward-port

Task

• [x] Implement go code to filter any "-rc" and/or "-rancher1" version strings from the asset versions.
• [x] Execute make auto-forward-port and check if it worked specifically for the case of the chart: rancher-vspher-cpi that was closed.

[nicholasSUSE]

I have just validated with rancher-vsphere-c** that the pattern for versions with -rancher* is ok and used in production. This task will only remove "-rc" versions.

[nicholasSUSE]

This is done @briandowns