as long as there is a manual Subscription, other automatic operators cannot be automatically installed or upgraded

[zhhray]

Bug Report

What did you do?

1. In the same ns, I need to deploy multiple operators, because the spec.targetNamespace of the operatorgroup under this ns is "", I want all-namespace operators to be installed in this namespace.
2. In the same ns, when I create a Subscription, spec.installPlanApproval is set to manual, but if I create multiple other spec.installPlanApproval automatic subscriptions. None of these operators are automatically approved, and they are all affected by the manual Subscription.
3. We can see the implementation in the code: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/pkg/controller/operators/catalog/operator.go#L1380
4. I want to know, why design it this way?

What did you expect to see?
I expect that the automatic Subscription is automatically approved and the manual Subscription is manually approved at any time, without influencing each other.

What did you see instead? Under which circumstances?
As long as the operator is deployed in the same namespace, the preceding problems must exist.

Environment

• operator-lifecycle-manager version: v0.26.0

• Kubernetes version information: v1.27

[zhhray]

Why, I wonder, is no one talking about this？