Open up traits for consumption by extensions

[Evangelink]

As of now, when using traits with MTP you have 2 options:

• MetadataProperty - used by TUnit, xUnit v3, TATF
• the internal serializable kvp property - used by the bridge

When an extension wants to act on this property it currently can do it only on MetadataProperty which won't work for VSTest bridge extensions (MSTest, NUnit...). The bridge should be changed to no longer use the serializable property but instead rely on the MetadataProperty.

Ideally, in order to reduce memory consumption, these properties should not always be emitted by the test framework and we should have a capability like we have for TRX that would allow clients or extensions to declare they are interested about such properties so that test framework can conditionally emit them.

[martincostello]

Any updates here? This issue is the only blocker I have for moving to MTP as it's needed to move Tyrrrz/GitHubActionsTestLogger#43 along.

[Youssef1313]

@martincostello There are no blockers for moving GitHubActionsTestLogger, except if you are using NUnit as VSTestBridge doesn't have a way to produce TestMethodIdentifierProperty for NUnit. The property is properly produced for MSTest, xUnit, and TUnit though.

[Youssef1313]

To clarify, this issue was a blocker in the past, but that was addressed in #5316. The issue is still open only to follow-up on a perf improvement:

Ideally, in order to reduce memory consumption, these properties should not always be emitted by the test framework and we should have a capability like we have for TRX that would allow clients or extensions to declare they are interested about such properties so that test framework can conditionally emit them.