Stop reusing same object to avoid beeing contaminated by previous test's operation

[ami-GS]

Description

ConnectionPriority test has been failing frequently at stream start order validation.
Increase sleep time for actually flush any remaining operations in processing queue
Cleanup and recreate MsQuic Objects for later test not to be contaminated by previous test's operation

Issue description
ConnPriorityOpTestIssue.pdf

Testing

Works 1000 times locally without sleep.
Need double check with CI

Documentation

N/A

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.72%. Comparing base (4316dbb) to head (9baef42).
Report is 31 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4615      +/-   ##
==========================================
- Coverage   87.02%   86.72%   -0.31%     
==========================================
  Files          56       56              
  Lines       17354    17361       +7     
==========================================
- Hits        15103    15056      -47     
- Misses       2251     2305      +54     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[nibanks]

Is there any way to make these event based? Is there some event we could wait on instead?

[ami-GS]

Maybe possible by ingesting dummy Operation on dummy Connection

[ami-GS]

Fixed only on Linux

[nibanks]

Can you add more details/explanation of the core problem and how this fixes it?

[ami-GS]

Before actually test starts (issuing StreamStart/StreamSend), implicit connection operations are processed.
When any stream operation, which have to be processed later, is inserted to the implicitly processed connection, the expected StreamStart/StreamSend order is messed up.
The sleep was to flush all these implicit operations.
I thought GetParam can also flush all operation as it is blocking call, but there is still error. I believe that any of implicit operation can be still potentially issued after GetParam call.