Cache Extension lifespan and maxidle behaviour

[karesti]

Describe the bug

When we don't provide any lifespan and maxidle, the default expiration configuration maxidle and lifespan configured in the cache should be used, if such exist. Providing -1, will ignore configuration values.

Expected behavior

If Quarkus users don't configure any expiration, the defaults of the cache should be applied. The workaround today is to set up the same values in config of the quarkus app

Actual behavior

Defaults are ignored

[quarkus-bot[bot]]

/cc @gwenneg (cache)

[karesti]

@gwenneg this is an infinispan cache extension issue only