Move CI check of trigger counts on data from TriggerTest to TrigP1Test

Move the ChainComp step comparing Trigger counts against a reference from test_trig_data_v1Dev_build.py (part of Trigger_athena_data CI test) to test_trigP1_v1Dev_decodeBS_build.py (part of Trigger_athenaHLT CI test). Additionally move also the doRuntimeNaviVal=True option.

Also update runTrigART.py to include the latter test in the "minimal" set of tests. Additionally reduce the number of events in that test from 80 to 50 for the convenience of local testing.

This aligns the strict checks with the two Trigger production workflows:

• MC Production, tested in Trigger_athena_MC CI test - unchanged here
• P1 data taking, tested in Trigger_athenaHLT - the one gaining stricter checks here

The workflows tested in the Trigger_athena_data CI test are important for Trigger software development but are not what we run in production so any stricter checks, like the counts comparison, should be applied to the other two.

This also prepares the CI configuration for the likely upcoming split of Tier-0/MCProd and P1 branches and projects. When that happens in a few months, Trigger_athenaHLT CI test will be only part of the P1 branch and Trigger_athena_MC only of the MCProd branch. We will only test MC trigger counts in MCProd branch CI and data trigger counts in P1 branch CI.

Jira: ATR-21857