Validate state of the test node to help adapters to give always expected information to the extensions/data consumers

Nobody has claimed this yet.

Ref https://github.com/microsoft/testfx/issues/3478#issuecomment-2329659440

At the moment "the platform" is nothing more than a IPlatformOutputDevice that collects an print in console or in server mode sent states outside. We don't have validation on what adapters are sending. We could think to add a "strict" verification of the state of every test node at least from the perspective of the lifecycle expected by the platform "at minimum"(you can push what you want if other extensions understand your shared model, like trx), like "discovered(non mandatory) -> in-progress(not mandatory) -> executionstate(mandatory)" rejecting with an exception if you push out of this expected state. cc: @Evangelink

Start with the linked Microsoft.TestFx issue and its referenced comment, then inspect how the platform receives test-node states from adapters. Done means the platform defines and enforces the expected lifecycle, rejecting out-of-order mandatory execution states while preserving supported extension behavior.

Written by the indexing model from the issue text.