Fix login detection on new LAVA versions

[mgalka]

In LAVA versions greater than 2020.02 "auto-login-action" has been renamed to "login-action". There is a need to handle both cases hence there are labs using older and newer LAVA instances. This fix makes KernelCI backend treat "login-action" or "auto-login-action" as a valid test case indicator depending on which one is present in the "lava" test suite provided by callback JSON.

[gctucker]

Please check on the frontend that we're now getting the login test case result for QEMU jobs in both lab-collabora and lab-baylibre, with lab-collabora still running 2020.02 and lab-baylibre a more recent version.

[mgalka]

Tests run with the fix

BayLibre Lab

baseline.login test case present - newer LAVA version

https://staging.kernelci.org/test/plan/id/5f879ac479fb446a13e5fcb8/ https://staging.kernelci.org/test/plan/id/5f8799547afcd7d353e5fcff/

Collabora Lab

baseline.login test case present - older LAVA version

https://staging.kernelci.org/test/plan/id/5f8795d7547659b7c1e5fd0b/ https://staging.kernelci.org/test/plan/id/5f8795e2e2b41215a0e5fcb8/

Tests run before the fix

BayLibre Lab

baseline.login test case not present - newer LAVA version

https://staging.kernelci.org/test/plan/id/5f84fa1978139bb5f49bf555/ https://staging.kernelci.org/test/plan/id/5f8486245b61a5363f960346/

Collabora Lab

baseline.login test case present - older LAVA version

https://staging.kernelci.org/test/plan/id/5f84f5f898510dfd8f9bf647/ https://staging.kernelci.org/test/plan/id/5f8484a9cc946ef6f6960357/