Add SDK build results in Grid view

The Grid view is designed for displaying test results. In the case where the SDK build job fails, no test job will be triggered. If the users only check Grid view, it is hard to know if there is no test build triggered for the platform (no action needed) or the SDK build job fails on the platform (triage is needed). If we can display failed SDK builds in Grid view, it will help users that only check Grid view to have an overall picture.

Challenges:
- SDK build name does not follow the common test build naming convention
- SDK build name: `jdk8u-linux-aarch64-openj9` (Adopt) and `Build_JDK8_ppc64_aix_Nightly` (Openj9)
- Test build name: `Test_openjdk8_j9_extended.openjdk_aarch64_linux` and `Test_openjdk8_j9_sanity.openjdk_ppc64_aix_Nightly`

- different Jenkins may have different build structure
- `jdk8u-linux-aarch64-openj9` is a parent job that triggers `Test_openjdk8_j9_extended.openjdk_aarch64_linux`
- `Build_JDK8_ppc64_aix_Nightly` and `Test_openjdk8_j9_sanity.openjdk_ppc64_aix_Nightly` are sibling builds

- There are SDK builds that do not trigger any test builds (i.e., internal jdk11u-linux-s390x-openj9). It is hard for TRSS to identify whether SDK build failure causes no test builds.

- SDK builds can fail after test builds are triggered. It is possible that the failure is related to infra/other jobs (i.e., Installer job). It is not related to SDK builds or downstream test builds.

The issue names no source files, tests, or entry points, so begin by locating the Grid view and the TRSS logic that gathers Jenkins SDK and test builds. Review how parent and sibling jobs are related before defining how failed SDK builds should appear. Done should make failed SDK builds visible in Grid view without misclassifying missing tests or unrelated downstream failures.

Written by the indexing model from the issue text.