Add new kuttl test for fully fledged frontend config

[florkbr]

Depends on #196 and the previous PRs @Hyperkid123 and I have already merged in.

This new test should flush out all the additional optional fields on a frontend resource. I want to keep both tests (basic-frontend) and this ensures we do not accidentally enforce new required fields if unnecessary.

[florkbr]

FWIW running this locally will pass no matter what until 196 is merged (we seem to ignore unrecognized fields). Once there is an entry for widgets in the struct, you can tweak this test and see the kuttl tests fail.

[Hyperkid123]

/retest

[adamrdrew]

09:03:37 [2024-10-17T13:03:37.963Z]     logger.go:42: 13:03:37 | full-frontend/1-create-resources | FrontendEnvironment:/test-full-app-environment created
09:03:37 [2024-10-17T13:03:37.963Z]     case.go:399: failed in step 1-create-resources
09:03:37 [2024-10-17T13:03:37.964Z]     case.go:401: Frontend.cloud.redhat.com "chrome" is invalid: [spec.widgetRegistry[0].defaults: Required value, spec.widgetRegistry[1].defaults: Required value]

[adamrdrew]

09:03:37 [2024-10-17T13:03:37.963Z]     logger.go:42: 13:03:37 | full-frontend/1-create-resources | FrontendEnvironment:/test-full-app-environment created
09:03:37 [2024-10-17T13:03:37.963Z]     case.go:399: failed in step 1-create-resources
09:03:37 [2024-10-17T13:03:37.964Z]     case.go:401: Frontend.cloud.redhat.com "chrome" is invalid: [spec.widgetRegistry[0].defaults: Required value, spec.widgetRegistry[1].defaults: Required value]

Should be an easy fix and then we can merge this