Fix RDS Redshift dynamic resources registration logic

[smallinsky]

What

The RDS Redshift resource types registered dynamically by tctl create -f db-resource.yaml are evaluated agains DB Service Resource Matchers.

Only DB Cloud Originated resources should skip ResourceMatchers evaluation logic.

Issue: #11285

[greedy52]

In the original ticket, the sample config is

db_service:
  enabled: yes
  resources:
    - labels:
        env: prod
        account: someaccount

Is that

[]ResourceMatcher{                                                          
        {                                                                                     
            Labels: types.Labels{"env": []string{"prod"}},                                    
            Labels: types.Labels{"account": []string{"someaccount"}},                                    
        },                                                                                                       
    }  

Or

 []ResourceMatcher{                   
        {                        
            Labels: types.Labels{                                                                 
                "account": []string{"someaccount"},                                                         
                "env":     []string{"prod"},                                                                
            },                                                                                                 
        },                                                                                                     
    }  

I feel it's the later one?

[github-actions]

@smallinsky See the table below for backport results.

Branch	Result
branch/v8	Create PR
branch/v9	Create PR