Switch non-ha profiles to use persistent local-cache configurations for web/ejb

Currently, the default configuration for distributable web applications in our non-ha profiles use a local-cache with file passivation support. While this configuration allows sessions to survive a restart, only passivated sessions will ever survive a server crash.
Considering feedback from users, a more sensible default would use a local-cache with a persistent file store.

Unfortunately, the name of the "web-passivation" layer name makes such a change problematic (frankly, this layer should never have been differently). Thus, we'll need to create a new layer (e.g. "web-persistence") that references a separate set of infinispan cache configuration feature-groups.