Adds hawt config properties to change appearance of the header and sidebar

[phantomjinx]

Overview

Since the Hawtio-Online dynamic console plugin has much more limited space, it is necessary to re-organise the UI components. Therefore,

• Being able to show/hide the header bar. This is no longer strictly necessary as the latest version of the console plugin still makes use of the header bar but figured this option was still useful, hence its inclusion;
• Being able to hide the brand logo. This is out of place in a sub-component tab of the OCP console and takes up a significant amount of space so essential to hide it;
• Being able to hide the User dropdown. This is redundant in the OCP console since the user is displayed at the top of the console, the Preferences are integrated in the console and logout action is redundant;
• Being able to hide the sidebar. The sidebar is wide and unnecessary. The console-plugin provides a toolbar dropdown that is applied to the header bar so much more compact.

Commit Changes

• Creates 'appearance' property group in hawtconfig with properties that determine whether

  • showHeader: to show/hide the main header bar
  • showBrand: to show/hide the brand logo in the header bar
  • showUserHeader: to show/hide the user header dropdown in the header bar
  • showSideBar: to show/hide the sidebar

• config-manager.ts

  • Introduction of Appearance type
  • Functions to fetch the value of the properties from a hawt config with the defaults being true if properties are not specified

• HawtioHeader.tsx / HawtioPage.tsx

  • Make the various components conditional according to the properties

[github-actions]

Test Results

  7 files   -  1    7 suites   - 1   1h 14m 17s ⏱️ + 10m 0s
 67 tests ± 0   65 ✅ ± 0   2 💤 ±0  0 ❌ ±0 
476 runs   - 68  451 ✅  - 65  25 💤  - 3  0 ❌ ±0 

Results for commit d829167. ± Comparison against base commit a9e8ad9.

♻️ This comment has been updated with latest results.

[hawtio-ci]

Test results

Run attempt: 3275
Detailed summary

NAME	TESTS	PASSED ✅	SKIPPED 💤	FAILED ❌	ERRORS 🚫	TIME 🕖
test-results-quarkus-node(18)-java(17)-firefox	68	65	3	0	0	640.769
test-results-quarkus-node(20)-java(17)-firefox	68	65	3	0	0	631.947
test-results-quarkus-node(20)-java(21)-firefox	68	65	3	0	0	652.308
test-results-springboot-node(18)-java(17)-firefox	68	64	4	0	0	630.058
test-results-springboot-node(18)-java(21)-firefox	68	64	4	0	0	639.557
test-results-springboot-node(20)-java(17)-firefox	68	64	4	0	0	635.973
test-results-springboot-node(20)-java(21)-firefox	68	64	4	0	0	627.325

[tadayosi]

Well, as I suggested before, the other way is to provide a HawtioHeadlessPage along with HawtioPage and the downstream app assembers can choose which page to use. I thought that approach was cleaner than introducing an omni option like the appearance to Hawtconfig.

But let's go with the option you proposed.