Use initial Quarkus Dev config for test tags and engines

[radcortez]

• Fixes Continuous testing exclude-tags or exclude-engines cannot be configured via pom.xml anymore in 3.13 #42714

It worked before because

quarkus/core/deployment/src/main/java/io/quarkus/deployment/dev/testing/TestTracingProcessor.java

Lines 95 to 102 in 7206ac0

	testSupport.setTags(config.includeTags.orElse(Collections.emptyList()),
	config.excludeTags.orElse(Collections.emptyList()));
	testSupport.setPatterns(config.includePattern.orElse(null),
	config.excludePattern.orElse(null));
	testSupport.setEngines(config.includeEngines.orElse(Collections.emptyList()),
	config.excludeEngines.orElse(Collections.emptyList()));
	testSupport.setConfiguredDisplayTestOutput(config.displayTestOutput);
	testSupport.setTestType(config.type);

sets the tags and engines config from the Quarkus Dev config (which includes the configuration coming from the build system).

With the change in #41317, handleApplicationPropertiesChange now sets the reading properties to empty List instead of null, which makes Object.equals to behave differently and override the configuration.

For now, let's fallback to the configuration set by TestTracingProcessor, but the goal is to improve this.

Related to:

• Register a Config instance to bootstrap tests #42715
• Confusing documentation or behaviour for quarkus.test.profile.tags #35693
• quarkus.log.file.path cannot be set for QuarkusTests via application.properties or .yaml #10233

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 39d19cc.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[gsmet]

Merged it but in the future, let's use List.of() for empty lists (no need to update it here, it's just a comment for future patches). Thanks!