Feature/make collection configurable

[heiglandreas]

This commit adds more configuration options to the
FormCollection-ViewHelper.

The hard-coded fieldset-wrapper is now configurable as is the hard-coded
legend as well as the hard-coded position and template of the
template-provider. The defaults have been set to the currently
hard-coded values, so that no BC-break should happen.

Also the behaviour of the template-renderer has been changed in so far
as the template is now rendered using the collection-object and not the
content of the collection-object

THis might be a case of BC-Break in edge-cases but the current
default-behaviour as provided by the unit-tests is not broken.

No tests have been changed, there have only been additions

This PR is a follow-up to #5565

[froschdesign]

Looks good to me. 👍

[Ocramius]

@Maks3w doesn't seem like there's any BC break here - can be thrown at develop IMO :D

[Maks3w]

This don't match default value.

[heiglandreas]

Thanks for spotting this typo. I'll just change that one to <fieldset>%2$s%1$s%3$s</fieldset>

[weierophinney]

@heiglandreas #5623 provides some logic to ensure that

1. legends will only be rendered if the fieldset has a label defined
2. fieldsets will render attributes as set on the collection

On merging your PR to the develop branch, I had a merge conflict due to those changes. I tried changing the $wrapper to read '<fieldset%s>%2$s%1$s%3$s</fieldset>', and altering the render() logic to inject the attributes, if any. However, this results in practically all of your new tests failing.

Any chance you can take a look at it?

[weierophinney]

I tried changing the $wrapper to read '<fieldset%s>%2$s%1$s%3$s',

This was wrong, once I paid more attention to the sprintf() invocation. I altered it as follows:

    '<fieldset%1$s>%3$s%2$s%4$s</fieldset>'

And the sprintf() invocation reads:

$markup = sprintf(
    $this->wrapper,
    $attributeString,
    $markup,
    $legend,
    $templateMarkup
);

This gets me closer - now only 2 failing tests. Will let you know if I get any closer.

[weierophinney]

@heiglandreas Got it! Merged to develop for release with 2.3.0.