Issues / proposals for handling NC Pins

1 - If a pin resolves to a no-connect "NC", then the test should fail quickly. Every test should start with an assert that checks that pins under test are not NC.

2 - Tests such as "tests-api-analogin" do not fail quickly when the pin under test is NC. It waits to time out and results in an Error and long wasted test time. It would be more useful if the test result was "NC" instead of "FAIL" or "ERROR"

3- It is unavoidable for some platforms to have some pins not connected (NC). This information is critical to users. It would be great if the CI Test Shield test end results also generated a Table with a list of the pins tested and the result, including if they are NC pins.

Start by locating the tests-api-analogin test and the CI Test Shield test-result reporting flow. Determine how pin resolution and timeout results are currently handled, then define how NC pins should be identified, reported without waiting for timeouts, and included in the final pin-results table.

Written by the indexing model from the issue text.