fix group function having placeholder code

I'm honestly not sure how this exception was being reached, in my own testing it did seem to progress, but it's also not what I originally wrote or intended to be in that function so I just re-implemented.

More bugfixes

fixed the InvalidExpressionException not being within the scope of the code

Exception handling bugfixes

not much in this update, just some fixes for ease-of-use when debugging authentication/connection issues

Bundled Purging, hashed tags, varnish proxy instance name config

NOTE: Make sure you delete the section_purger folder from modules before you update to this version as the tags header module was merged into the purger module for the sake of consistency as well as (now) required dependency.
-SectionBundledPurger added - will bundle tag purges into one API call
-Cache tags are now hashed for shortening data and privacy/security
-The header for cache tags must now be Section-Cache-Tags
-Varnish proxy instance names are now configurable. Read more in readme
-Raw VCL expression invalidations are now their own type: raw. Resultingly, regex invalidations now follow convention.

Support all invalidation types & implement key module for safe password storage

Fairly major code renovations. Totally reworked how invalidations are handled so it can support all types, not just tags.

v0.0.6

This release removes an unused gitignore file that hindered build artifacts for some customers. Ref: #9

Changes:
Remove gitignore: #10

v0.0.5

This release normalizes the metadata associated the Section purger and updates the configuration check file to reference the new purger instead of the no longer extant HTTP module.

Support for Non-Production domains

This change allows users to link a drupal instance with a non Production domain within the section platform.

Naming Conflict Fixes

Some of the naming across labels and id's in the purger left open potential for naming conflicts and ambiguity for certain users running additional purgers. This release customizes them to Section to remove this ambiguity.

Introduce Multisite Support

This release provides Drupal8 multisite support. Previously, when a user had a drupal multisite and configured each domain to point at the same Section environment, clearing cache for a resource on one site would clear cache for all sites with the same resource URL/cache tags. As a part of implementing this feature, configuring the purger now has an optional site name field, which will scope cache bans to that specific site.

This release also also accomplishes minor cleanup actions such as removing the ability to change the Aperture base url via the purger configuration form.