fix: third-party apps should use the qualified certification

[nataliepina]

What problem does this PR solve?:
Third-party applications should use 'qualified' instead of 'supported'.
Supported is now reserved for Nutanix supported apps - NKP Insights, NAI, etc.

Which issue(s) does this PR fix?:

https://jira.nutanix.com/browse/NCN-105258

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

CloudNativePG and Harbor applications will have a qualified badge and not a certified badge.

Checklist

• If the PR adds a version bump, ensure there is no breaking change in Licensing model (or NA).
• If a chart is changed or app configuration is significantly changed, the chart version is correctly incremented (so that apps are not automatically upgraded from a previous version of DKP).

[coveralls]

Pull Request Test Coverage Report for Build 12813265114

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 51.703%

---

Totals
Change from base Build 12807820042:	0.0%
Covered Lines:	167
Relevant Lines:	323

---

💛 - Coveralls

[guillermoz-nutanix]

I agree an app shouldn't have both supported/qualified.

The trick with Nutanix registry is that we are adding extra configuration to make it HA, eg, deploying PG and Valkey(Redis) as dependencies, so this is not an app that we simply bundle.

I'm not sure where the boundary between Qualified and Supported apps lives.

[nataliepina]

I agree an app shouldn't have both supported/qualified.

The trick with Nutanix registry is that we are adding extra configuration to make it HA, eg, deploying PG and Valkey(Redis) as dependencies, so this is not an app that we simply bundle.

I'm not sure where the boundary between Qualified and Supported apps lives.

Yeah, I am following the notes from product on this. There may need to be further discussion around this.