PA Migration: Update L0_client_build_variants

[fpetrini15]

The objective of L0_client_build_variants is to build client libraries/binaries by enabling/disabling various optional features and verify that the build succeeds.

One such set of combinations is to enable/disable optional PA features and verify the build succeeds. This test had been passing (false positive) despite running with a client branch that purged PA from the client repo. Examining the logs closer, it was because CMake was simply ignoring PA-related parameters and repeatedly performing the same standard cc-client/python-client build:

Manually-specified variables were not used by the project:

    TRITON_ENABLE_PERF_ANALYZER
    TRITON_ENABLE_PERF_ANALYZER_C_API
    TRITON_ENABLE_PERF_ANALYZER_TFS
    TRITON_ENABLE_PERF_ANALYZER_TS

These changes modify the script to point to PA source code that recognizes these optional parameters, restoring the test's original purpose.

Ideally, these tests will eventually be moved out of Triton CI entirely and into PA CI.

[rmccorm4]

I was going to ask if we could detect and raise an error to catch these "unused variables" silent issues, but it seems like a common problem with no clear solution (from 2min of research):

• https://discourse.cmake.org/t/cmake-warnings-as-error/3960/4
• https://stackoverflow.com/questions/54461491/cmake-stop-if-a-manually-specified-variable-is-not-used-by-the-project
• https://discourse.cmake.org/t/fail-cmake-if-there-are-unused-variables-defined/840

So I suppose there's no quick check we can do on our end, other than parsing the output with some custom logic.

[rmccorm4]

LGTM other than adding follow-up ticket comment

[rmccorm4]

Great description and nice catch 🚀