Inconsistent behavior - dev mode overrides looseApplication=false in plugin parameter config but not property config

[scottkurz]

Though clearly dev mode is designed assuming the use of loose applications, it is still useful with loose application support disabled. See discussion: #1817

However, the intention at one point was to disable a looseApplication=false setting and force the user to run with the default looseApplication=true.

However, this override behavior was incompletely implemented. It was only implemented for plugin parameter config, but not properties.

Presumably this was an oversight at the time? There are other areas like the rework of the dev mode "skip" config where I believe we've tried to treat plugin & property config similarly.

Though one conceivable option would be to begin override the property behavior as well, like the parameter config, I think there is value in allowing this, as mentioned in the discussion above.

We could also simply stop overriding the parameter config.

Consider though a user that relies on loose app = false for some other use case, say some kind of custom Docker build. Perhaps that user has gotten used to also running dev mode.

Should we just leave things as-is then?