Difference in OpenTracing subsystem standard configuration leads to the tests failures

Since OpenTracing has been introduced, `standalone.xml` had the following OT SmallRye subsystem configuration:

<subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0" default-tracer="jaeger">
    <jaeger-tracer name="jaeger">
        <sampler-configuration sampler-type="const" sampler-param="1.0"/>
    </jaeger-tracer>
</subsystem>

With WildFly 19 and later we also have `standalone-microprofile.xml` configuration file which is used by default in MicroProfile test suite [1]. It has the following configuration:

<subsystem xmlns="urn:wildfly:microprofile-opentracing-smallrye:2.0"/>

As it is recommended in documentation [2] it's better to define missing Jaeger properties (sampler type _and _sampler param) in order to sample every request. Sampling every request is needed by MicroProfile test suite OpenTracing basic tests.

A question is: will `standalone-microprofile.xml` configuration file have the wider OT subsystem configuration? Or do the tests have to define additional attributes in subsystem by themselves?

Thank you.

[1] - https://github.com/jboss-eap-qe/eap-microprofile-test-suite#target-distributions-and-microprofile-specs
[2] - https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html/configuration_guide/eclipse_microprofile