The primary objective of this task is to streamline the user interface and user experience for managing build and workload secrets. 

Currently, the Component creation dialog involves the creation of SPITokenBinding. We propose migrating to plain k8 Secret. This transition will involve updating the Component creation dialog to create Secrets instead of SPITokenBindings.

Here is an example of how the Secret might be structured:

apiVersion: v1
kind: Secret
metadata:
  namespace: default
  name: test-scm-secret
  labels:
    appstudio.redhat.com/credentials: scm
    appstudio.redhat.com/scm.host: github.com
  annotations:
    appstudio.redhat.com/scm.repository: mshaposhnik
type: kubernetes.io/basic-auth
stringData:
  password: Z2hw....

More about label and annotation can be found here https://docs.google.com/document/d/1KONMhCSJxq17bOInbMErVQm25FUGM6OA-DLQV5hFBsY/edit#heading=h.hzjv4g8yo2c0

Open questions:

• Should this epic also include simplifiction of code import and not use SPIAccessCheck to validate URLs?
• Should this epic also include refinement of the Secrets list and secrets creation dialog?  See more https://issues.redhat.com/browse/KONFLUX-266 
  https://docs.google.com/document/d/1xXeMcqjXYkzB6dCdTeu0k2k6aRWQZqGtvhib3eaPeFk/edit#heading=h.nk0gqur98cd3