Enhance platform requirements mechanism for TKG

We are using `` to specify the spec to test against. It provides some degree of freedom to define os, arch, bit information, but it's limited (only support and relationship) and sometimes difficult to read and write.

A better way is to utilize regular expression to define the platform. Another step to improve the mechanism to use platform instead of spec to define the information. Since they are more clear and intuitive because it matches the build names.

Start by locating the code that parses and applies in TKG, then review how build names expose platform information. Define the regex-based platform matching and platform-based configuration behavior, with completion shown by coverage of OS, architecture, and bitness cases.

Written by the indexing model from the issue text.