Fix client-tag selector rule in presto-router

[saravanan19]

Description

When the client-tags matches the request, the selector should choose the target group. The bug in the code doesn't do that. In th current code, when all the client-tags match incoming request, the selector is not matched.

Motivation and Context

When the client-tags matches the request, the selector should choose the target group. The bug in the code doesn't do that. In th current code, when all the client-tags match incoming request, the selector is not matched.

Impact

None

Test Plan

Verified manually by passing client-tags in the request and tried to match the client-tags configured in the selector. After the fix, it matches and the right target group is used

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* ... :pr:`12345`
* ... :pr:`12345`

Hive Connector Changes
* ... :pr:`12345`
* ... :pr:`12345`

If release note is NOT required, use:

== NO RELEASE NOTE ==

[linux-foundation-easycla]

• ❌ - login: @saravanan19 / name: Saravanan balasubramanian . The commit (bf53dfe) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[tdcmeehan]

Any way to add a unit test?

[tdcmeehan]

@saravanan19 ping