[REGRESSION]: VSTest@3 does not use narrower pattern

[nohwnd]

New issue checklist

• I searched for existing GitHub issues
• I read pipeline troubleshooting guide
• I checked how to collect logs

Task name

VSTest@2

Breaking task version

3

Last working task version

2

Regression Description

The new task does not use the narrower test pattern implemented in #17135. This breaks our users, because they end up resolving additional dlls in obj and bin.

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

all

Relevant log output

I don't have logs, this is caused by the task configuration.

Full task logs with system.debug enabled

UNSUCCESSFUL RUN

 [REPLACE THIS WITH YOUR INFORMATION] 

SUCCESSFUL RUN

 [REPLACE THIS WITH YOUR INFORMATION] 

Repro steps

# Starter pipeline
# Start with a minimal pipeline that you can customize to build and deploy your code.
# Add steps that build, run tests, deploy, and more:
# https://aka.ms/yaml

trigger:
- main

pool:
  vmImage: ubuntu-latest

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

- script: |
    echo Add other tasks to build, test, and deploy your project.
    echo See https://aka.ms/yaml
  displayName: 'Run a multi-line script'

- task: VSTest@2

- task: VSTest@3


Put this in interactive pipeline editor on AzDO. 
click settings above VSTest@2 and you will see the new filter:
**\bin\**\*test.dll
**\bin\**\*tests.dll

click settings above VSTest@2 and you will see old filter:
**\*test*.dll
!**\*TestAdapter.dll
!**\obj\**

[nohwnd]

@v-gayatrij did something happen? will this be reverted / fixed?