Camel IT failing on Fedora + Bash due to environment variables containing bash scripts with variables

[gsmet]

On Fedora + Bash, the Camel IT tests are failing with this error:

Caused by: java.util.NoSuchElementException: Property IFS+x not found
	at io.smallrye.config.SmallRyeConfig.getValue(SmallRyeConfig.java:89)
	at io.quarkus.runtime.configuration.ConfigExpander.accept(ConfigExpander.java:55)
	at io.quarkus.runtime.configuration.ConfigExpander.accept(ConfigExpander.java:15)
	at org.wildfly.common.expression.ExpressionNode.emit(ExpressionNode.java:42)
	at org.wildfly.common.expression.CompositeNode.emit(CompositeNode.java:42)
	at org.wildfly.common.expression.Expression.evaluateException(Expression.java:75)
	at org.wildfly.common.expression.Expression.evaluate(Expression.java:89)
	at io.quarkus.runtime.configuration.ExpandingConfigSource.expand(ExpandingConfigSource.java:46)
	at io.quarkus.runtime.configuration.ExpandingConfigSource.getValue(ExpandingConfigSource.java:38)
	at io.smallrye.config.SmallRyeConfig.getValue(SmallRyeConfig.java:74)
	at io.quarkus.camel.core.deployment.CamelIntiProcessor.createInitiTask(CamelIntiProcessor.java:61)

This is due to the BASH_FUNC_* environment properties containing things like that:

if [ -n "${IFS+x}" ]; then

as MP Config tries to expand the variable and fail.

What makes the Camel ITs specific is that they iterate over all the configuration properties to push them to Camel.