Environment filters in the Home and Space page LiveTables don't always match the values shown in the columns

The Browser, Database, Servlet Container, Java and Distribution filters added in TESTREPORT-50 can keep tests that don't show the filtered value, and drop tests that do.

Steps to reproduce

1. Create a test with two executions that have the same date but different products, for example XWiki 17.10.3 on Google Chrome 117 and XWiki 18.7.0 on Mozilla Firefox 140.
2. Create a second test whose latest product was tested on a browser page named QA.Chrome 117, with name "Google Chrome" and version "117". Test an older product on QA.Google Chrome 117.
3. On the test space home page, filter the Browser column on "Google Chrome 117".

Expected result

The filtered table shows exactly the tests whose Browser column shows Google Chrome 117.

Actual result

• A test from step 1 whose column shows Google Chrome 117 can be missing, and one whose column shows only Mozilla Firefox 140 can be listed. Which one depends on the order in which the executions were saved.
• The test from step 2 is missing, although its column shows Google Chrome 117.

Cause

The filter and the column in QA.LiveTableResults don't compute the value the same way:

• Latest execution: when several executions share the latest date, the column takes the first row of order by execution.date desc, which doesn't define which one comes first. The filter takes the one with the highest object id. So they can end up on different products.
• Environment identity: the column groups environments by the name and version of the environment page. The filter matches the exact page reference. Two pages with the same name and version look the same in the column, but only one of them matches the filter.

Proposed fix

• Expand each environment filter value into every page of the same environment class with the same name and version (name only for Distribution). Keep the value as it is when it isn't an environment page.
• Use the same tie-break on both sides: order the column's latest execution by date, then by object id, like the filter does.