KENG artifacts renaming, plus introduction of the license server

[bortok]

We have three categories of changes, and they are interconnected, so bundling them all together:

• Aligning names of some artifacts with the official product name “Keysight Elastic Network Generator”,
• Introducing licensing enforcement for advanced capabilities of “Keysight Elastic Network Generator”,
• Changing docker image path and access for some artifacts enabled by the licensing enforcement.

Old name	New name
ixia-c-controller	keng-controller
ixia-c-operator	keng-operator
ixia-c-ixhw-server	keng-layer23-hw-server
ixia-c-app-usage-reporter	keng-app-usage-reporter
ixia-c-gnmi-server	otg-gnmi-server

Ixia-c name becomes tied only to the type of the KENG Test Ports that are container-based SW, as opposed to L23 Hardware or UHD400T.

The changes related to the licensing:

• LICENSE-SERVERS env var for keng-controller supplied via docker-compose YAML for HW or keng-operator for KNE setups
• Configmap for the keng-operator to provide a value for the LICENSE-SERVERS
• License Server VM is needed with a valid license

We’re changing visibility of some previously private images to become public, and therefore their docker image paths are changing as well:

Old private path	New public path
ghcr.io/open-traffic-generator/licensed/ixia-c-controller	ghcr.io/open-traffic-generator/keng-controller
ghcr.io/open-traffic-generator/licensed/ixia-c-protocol-engine	ghcr.io/open-traffic-generator/ixia-c-protocol-engine
ghcr.io/open-traffic-generator/ixia-c-ixhw-server	ghcr.io/open-traffic-generator/keng-layer23-hw-server

[bortok]

check if fails with 0.13

[bortok]

check if works with 0.13

[bortok]

check if 0.13 works