OdhApplications Have Non-Uniform States for Support & Category

Description of problem:

We have several OdhApplication CRs that show up now in RHODS (and upstream ODH) that do not possess a consistent usage for `category` and `support`.

Our current categories (as we know it) are:

• Red Hat managed
• Partner managed
• Self-managed

I asked about alternatives and was told this was all we had in RHODS-5414 (comment)

There is however an "ODH Core" category for Pipelines (link)

Our `support` field has inconsistent values:

• redhat (RHODS repo)
• red hat (ODH repo)
• Open Data Hub (ODH repo)
• third party support (both)

These are not standardized – should they be?

Source:

• Raw filter for RHODS org on GitHub
• Raw filter for ODH org on GitHub

Expectations

I'd think we should have a concrete set of settings. Category probably should be confined to an enum of values via a CRD. Support is up in the air I guess – we should find a way to be consistent within' our own set of upstream/downstream items.