Add developer edition package flavors

[Racer159]

Is your feature request related to a problem? Please describe.

As Kay I want access to the developer (licensed) version of SonarQube so that I can scan my C/C++ projects in SonarQube as well.

Describe the solution you'd like

• Given I am adding SonarQube to a bundle
• When I add -upstream-developer or -registry1-developer to the end of my ref
• Then the developer edition of SonarQube is included in my bundle

Additional context

This is needed to support additional languages and features that folks will want.

[Racer159]

We will also need to build/ship an improved sonarscanner image that has C support.

[Racer159]

After talking to @zachariahmiller on this after the community edition split to be date-based versioning it would likely be best to do something like:

10.8.0-uds.0-developer-upstream
10.8.0-uds.0-developer-registry1

with the flavors being distinct from the community counterparts without the type prefix (so community would be something like 24.12.0.100206-uds.0-registry1)

this would allow versioning to still follow <semver>-uds.<uds-ver> to work with our existing upgrade logic that requires unique flavor names (Zarf also expects flavor names to be unique)