Suspend will be triggered twice on an UMA or a non-switchable hybrid system

Assigning to Sam as he's working on the GPU tests now.

Dependency chart for this case attached, you can see the issue here
(suspend will be triggered twice, because we're not using the generated local job for the two suspend job)

For this suspend-twice issue, there are several possible solutions, but all with different issues.

* Solution A:
Ask suspend_advanced to depend on 2_switch_card test
therefore it won't be executed on UMA system

However, this would cause those "OTHER AFTER SUSPEND TESTS" to be skipped.

* Solution B:
Move suspend_advanced job, make it act as the suspend job for the 1st card
add dependency to the graphic_switch test, make sure it's running on
the correct GPU, and change the "suspend/1_suspend_after_switch_to_card" into
"suspend/2_suspend_after_switch_to_card" for 2nd card.

However, there are some jobs for graphics after suspend on 2nd card still
depend on suspend_advanced, if we do this, it will still be triggered due to
the dependency setting, unless we will remove the dependency

* Solution C:
Remove the suspend_advance job totally, replace it with the one generated by
the local job. This could help us to create some dependency for those job that
does not have a dependency yet (e.g. suspend/2_suspend-time-check)

Howevere, this will cause some problem to those "OTHER AFTER SUSPEND TESTS",
the suspend_advanced is no longer available, we have to move the dependency to
one of the suspend test generated by the local job (ideally to the suspend
test of 1st card). But the issue is that we can't use the dependency of
depends: suspend/1_suspend_after_switch_to_card_.*
nor
depends: suspend/1_suspend_after_switch_to_card_`echo "${product}" | sed 's/ /_/g;s/[^_a-zA-Z0-9-]//g'`

Another thing is that if we move "OTHER AFTER SUSPEND TESTS" to the place where we test card 1
e.g. from:
suspend-card2
OTHER AFTER SUSPEND TESTS
hibernate-card2
switch-card1
suspend-card1
hibernate-card1

to:
suspend-card2
hibernate-card2
switch-card1
suspend-card1
OTHER AFTER SUSPEND TESTS
hibernate-card1

it will work perfectly on UMA system, but on a hybrid graphic system, they will be triggered after the hibernate test for card 2, I'm not sure if this is acceptable.

Dependency chart for solution A

Dependency chart for solution B

* Solution D
Adapted from solution B,
Move suspend_advanced job, make it act as the suspend job for the 1st card
add dependency to the graphic_switch test, make sure it's running on
the correct GPU, and change the "suspend/1_suspend_after_switch_to_card" into
"suspend/2_suspend_after_switch_to_card" for 2nd card.
And not to use all the jobs generated by the local job, so we can change the dependency for 2nd card to the "suspend/2_suspend_after_switch_to_card" job itself, make them not depend on suspend_advanced.

Testing branch now

Dependency chart for solution D

Dependency chart for solution D updated
Making suspend_advanced not depend on 1_switch_card job, since it will need to be written as:
depneds: graphics/1_switch_card_*
But this kind of expression is only available in local jobs.