Description of problem:

The Tekton Operator's reconciliation loop is removing the `catalog-{INDEX}-type` field  (e.g., `catalog-1-type: tektonhub`) , preventing users from configuring custom hub catalogs through the TektonConfig CR.

Root Cause:
The `ConvertPacStructToConfigMap` function in  `pkg/apis/operator/v1alpha1/openshiftpipelinesascode_defaults.go` was not writing 
the `catalog-{INDEX}-type` field when converting hub catalogs back to ConfigMap format. This causes the operator to drop custom hub catalog type specifications on every reconciliation cycle.

Impact:

• Users cannot configure custom hub catalogs (TektonHub, ArtifactHub, or custom hubs) 
    via TektonConfig CR
• The catalog type field is removed even if manually added to the ConfigMap
• Prevents customers from using TektonHub or other custom hub implementations

  Prerequisites (if any, like setup, operators/versions):

  Steps to Reproduce

 # <steps>

Actual results:

The operator only writes three fields for custom catalogs:

• catalog-{INDEX}-id
• catalog-{INDEX}-name
• catalog-{INDEX}-url

The catalog-{INDEX}-type field is dropped, preventing proper hub catalog configuration.

Expected results:

The operator should preserve all four required fields for custom hub catalogs:

• catalog-{INDEX}-id
• catalog-{INDEX}-name
• catalog-{INDEX}-type
• catalog-{INDEX}-url

The catalog type field should be maintained in the pipelines-as-code ConfigMap 
during operator reconciliation cycles.

Reproducibility (Always/Intermittent/Only Once):

Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *