chore: simplify secrets management in release workflow by inheriting secrets (#1397)

On-behalf-of: Gerald Morrison (SAP) <gerald.morrison@sap.com>
Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>

<!-- markdownlint-disable MD041 -->
#### What this PR does / why we need it
simplify secrets management in release workflow by inheriting secrets

Signed-off-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
Co-authored-by: Gerald Morrison (SAP) <gerald.morrison@sap.com>
Co-authored-by: ikhandamirov <108289993+ikhandamirov@users.noreply.github.com>

Author: 3 people

.github/workflows/release.yaml

@@ -274,12 +274,7 @@ jobs:
     uses: open-component-model/.github/.github/workflows/bdba.yaml@main
     with:
       artifact_id: ctf-aggregated
-    secrets:
-      BDBA_API_TOKEN: ${{ secrets.BDBA_API_TOKEN }}
-      BDBA_URL: ${{ secrets.BDBA_URL }}
-      BDBA_GROUP_ID: ${{ secrets.BDBA_GROUP_ID }}
-      BDBA_USERNAME: ${{ secrets.BDBA_USERNAME }}
-      BDBA_PASSWORD: ${{ secrets.BDBA_PASSWORD }}
+    secrets: inherit
     permissions:
       contents: read 
       actions: read