Support for .htaccess files

[tombuildsstuff]

Added a means of setting the apache AllowOverride setting (required to allow .htaccess files) - defaults to 'None' in the Apache::VHost resource

[igalic]

do we need a README update for this?

[tombuildsstuff]

@igalic happy to update it - just let me know :)

[ffrank]

Yes, please. Feel free to squash commits, but in this case I would be fine with a two commit branch.

What's wrong with PCCI? Thoughts @nibalizer?

[Note, I'm a little sad that we have to expose Apache options this way, but what are you going to do.]

[igalic]

[@ffrank: you could do something like PUP-4669]

[ffrank]

[@igalic well, -ish. Where the main interface of a module is concerned, this pattern will likely not match, because you can easily have several resources like that which you want to be configurable.]
[[Meta-convo this way feels silly and I love it.]]

[igalic]

[@ffrank: yes, but you could always use an $apache_* prefix which you'd use to forward to the apache vhost…, and perhaps a different prefix for, say, $vcsrepo_*, as also described in said issue]

[tombuildsstuff]

@igalic @ffrank sorry - what is it you want me to do here? squash the commits and add documentation?

I guess the other way to handle this would be a default hash provided in this class - with overrides passed in and merged together using an ensure_resource?

[igalic]

sound good, yes!

[jyaworski]

Hello:

What is the status of this PR? Is it just failing PCCI, and can we merge regardless?