using bitwarden secrets in different namespace from sm-operator should be working without authToken

[victorbiga]

Steps To Reproduce

1. Create secret in bitwarden UI
2. Create secret in different namespace to where sm-operator is deployed

Expected Result

INFO	Syncing  sm-operator/bitwardensecret-sample	{"controller": "bitwardensecret", "controllerGroup": "k8s.bitwarden.com", "controllerKind": "BitwardenSecret", "BitwardenSecret": {"name":"bitwardensecret-sample","namespace":"sm-operator"}, "namespace": "sm-operator", "name": "bitwardensecret-sample", "reconcileID": "7dased4f-a07f-48e2-b329-e68004142902"}

Actual Result

"error": "Secret \"bw-auth-token\" not found"}

Creating secret in different namespace should work without providing below, this should be handled by the operator

  authToken:
    secretName: bw-auth-token
    secretKey: token

This is deployed in sm-operator namespace and referencing this secret across namespace is not possible without replication.

Screenshots or Videos

No response

Additional Context

No response

Chart Version

0.1.0-Beta

Environment Details

kubernetes 1.31

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.