Issues with SBOMScanner Backend Installation via SBOMScanner UI Extension

[esther-suse]

Description:
The current installation process for the SBOMScanner backend through the UI extension is interrupted by a missing namespace error.
Additionally, the sequence of configuration steps is unintuitive for the end user.

Steps to Reproduce:

1. In a fresh installed K3S VM, Navigate to the SBOMScanner page and click "Start Installation."
2. Step 1: Click "Add the CNPG Helm repository."
3. Step 2: Provide credentials for the SBOMScanner Helm repository, uncheck "Skip TLS Verification" and "Insecure Plain HTTP," and click "Add SBOMScanner repository."
4. Step 3: Click "Install CloudNativePG" and wait for successful deployment.
5. Return to the SBOMScanner page to begin the SBOMScanner Installation. Input the Image Pull Secret, click "Next," then click "Install."

Actual Results:
The installation fails with the error: namespace "cattle-sbomscanner-system" not found.
The user must manually create the namespace via CLI before the installation can proceed.

Expected Results:
The cattle-sbomscanner-system namespace should be created automatically by the extension during the installation process.

Issue about Logical Workflow :
The current logic mixes repository configuration for two different components.
To improve the user experience, I propose grouping the "Repository Add" and "Install" actions for each component together.

Current Logic: Add the CNPG Helm repository --> Add the SBOMScanner Helm repository --> Install CloudNativePG --> Install SBOMScanner

Proposed Logic: Add the CNPG Helm repository --> Install CloudNativePG --> Add the SBOMScanner Helm --> Install SBOMScanner

[xingzhang-suse]

To fix the namespace creation issue, I enabled the namespace selector

For the installation workflow, as the installation will redirect user to Rancher UI's installation page which is out of UI extension scope, it will let the user to go out of the UI extension and back again twice. But the current workflow only need to be only once. We'd like to hear some feedback from the user in future.

[esther-suse]

The namespace issue is fixed in 0.8.0-rc1 build.
Per developer's suggestion, we will keep current workflow.