Allow for unanchored UserDir filename patterns

The change made in https://github.com/puppetlabs/puppetlabs-apache/commit/b1a3cc18f3d07ec239b5183384c12798f83b852f seems to forcibly anchor all UserDir lookups to a single path prefix. "$home/*/$dir" doesn't allow for using the ~username lookup via the system's name service to determine home directory, which is needed in cases where there are multiple home directory paths possible.

Because the UserDir string hardcodes the /*/ in the middle it leaves no wiggle room to creatively use $home, either.

I'm not sure what to do about ensuring it matches the singular 'free' <Directory "$home/*/$dir" > element. In our particular instance, we have to specify the alternate home paths elsewhere in the config. Make $home into a $homes array and using UserDir's facility to have more than one filename pattern and directory block would probably work for our particular situation, but might not fit in with other's needs. Perhaps make the free directory block something you can opt out of?