In the TCK parameters to Assert.assertEquals are reversed in some cases

[tjquinno]

Describe the bug

At least some code in the TCKs reverses the expected and actual parameters in the Assert.assertEquals method invocations.

One example:

microprofile-telemetry/tck/tracing/src/main/java/org/eclipse/microprofile/telemetry/tracing/tck/rest/W3BaggagePropagationTest.java

Lines 110 to 111 in 5ab478e

	Assert.assertEquals(BAGGAGE_VALUE, server.getAttributes().get(BAGGAGE_VALUE_ATTR));
	Assert.assertEquals(BAGGAGE_METADATA, server.getAttributes().get(BAGGAGE_METADATA_ATTR));

The first parameter should be the actual value and the second the expected value

https://javadoc.io/static/org.testng/testng/7.10.2/org/testng/asserts/Assertion.html#assertEquals(boolean,boolean)

public static void assertEquals(int actual, int expected )

but they are reversed here (and possibly elsewhere).

If the implementation works correctly then the assertion passes anyway, so this is not a big problem but should be addressed eventually.