[TASK] Only resolve file paths for the usual Fluid paths in Path Utility
[FEATURE] Add extensionName argument when reading Flux forms

This will create a RenderingContext and a ControllerContext with that extension name when reading Flux form variables stored in templates. The extension name can be used automatically by ViewHelpers like `f:translate` but can also be read by Flux to build automatic LLL values for Flux form fields.
[TASK] Use extension name when building Data Structure for FlexForm display

This will pass the extension name as detected by either TypoScript settings or collection key name (fx fluidcontent_bootstrap) used in the TypoScript configuration.
[TASK] Switch to fixed Path Utility in Configuration Service
[TASK] Use configured extension name in Content Service
[TASK] Inject Debug Service in FlexForm related ViewHelpers
[DOC] Add missing in-method variable type declaration
[TASK] Detect extension name from file reference only if not given as argument
[FEATURE] Add extensionName argument on Exposed Standalone View
[TASK] Switch emulated Request with passing of extension name to Exposed View
[FEATURE] Label fetch method on all FlexForm related ViewHelpers

Using this method either reads the label from ViewHelper's attributes or creates an automatic LLL reference based on the ViewHelper type (sheet, object, field etc) and name.
[TASK] Change prefix name for raw fields from empty string to "fields"
[TASK] Add recognition of Section ViewHelpers in Abstract FlexForm ViewHelper
[TASK] Add recognition of Content ViewHelpers to Abstract FlexForm ViewHelper
[FEATURE] Optional labels on flexforms, sheets, objects, areas and fields

Utilises the newly added automatic LLL insertion to make the `label` attribute on the mentioned ViewHelpers optional. If not added, special LLL references will be built instead (enabling the debug feature provides verbose information).

Some ground rules:

* Works only on Flux forms registered with an appropriate extension key relation, which can be achieved in three ways: 1) Use the extension key as index when adding the collection paths. 1) When adding TypoScript paths for your collection, add an "extensionKey" attribute next to the path definitions (useful if you can't or won't use the extension key as index). 3) Once registration through PHP becomes possible, the relation is made whenever PHP registration is used.
* Only generates an LLL reference if a label was not specified on each individual entity.
* Prefixes every reference in the TCE array with `LLL:EXT:extensionkey/Resources/Private/Language/locallang.xml:flux.` to isolate automated labels. Should automatically work with XLIFF thanks to to internals in TYPO3.
* Displays a completely empty label if no LLL value was found for the current language - this is expected TYPO3 behaviour but can be hard to investigate.

Example automated labels:

* …:flux.objects.fluxFormId.objectName
* …:flux.objects.fluxFormId.objectName.fieldNameInObject
* …:flux.flexforms.fluxFormId
* …:flux.sections.fluxFormId.sectionName
* …:flux.fields.fluxFormId.fieldNameNotInObject
* …:flux.areas.fluxFormId.contentAreaName
[TASK] Change description of label attributes to proper LLL example
[TASK] Add new extension name capability to Grid Service
[FEATURE] Shortcut method to getStoredVariable on FlexForm Service
Merge pull request #62 from NamelessCoder/labelsoptional

[FEATURE] Optional label attributes, automated LLL reference building