SHA-1 is still supported but needs to be configured explicitly if you need it.

Per suggestion from @jaimeperez, rename the undocumented
noconsentattributes option to be more consistent with other things and
with what has been done in the ConsentAdmin module. The old version
remains supported for backwards compatibility but issues a warning.

Fixes https://github.com/simplesamlphp/simplesamlphp/issues/841

The Consent module has a (currently undocumented) noconsentattributes
option that allows specified attributes to be removed from the consent
hash calculation. The noconsentattribute option was introduced at
simplesamlphp/simplesamlphp@1efcfa8 but no corresponding option
was added to the consentAdmin module. Thus if people are using the
noconsentattribute option to remove attributes, the consentAdmin module
will *always* show this as attribute values having been changed.

This is a rework of simplesamlphp/simplesamlphp#531 which has gotten corrupted over time.

This reverts commit ef36c5fd.

All a bit too involved right before a planned release.

Also, convert to PSR-2 where that was still lacking in these files.

Enhancements to AttributeLimit to give additional control over allowed values

It can be useful to see the AuthData when testing an authentication source.

Since the AuthData can be a hierarchy of data of various depths it is converted
into a pretty printed JSON structure.

Since the amount of AuthData can vary greatly, the data is displayed in side
a `<details>` element which requires clicking to view.

To aid administrators in finding the root cause of an XML parse fail,
we should return the error message we got from the underlying parser.

* Add authproc filter to test correct cardinality

Attribute schemas often have specific requirements for the number of
values a particular attribute may have, and violating the cardinality
rules associated with these may have unexpected and undesirable results.

The two authproc filters this change introduces allow the cardinality of
attributes to be tested. core:Cardinality is the more general case, and
allows for both a minimum and maximum number of values to be tested.
Processing will abort with an error if too few or too many are received.

core:CardinalitySingle is a special case of this for single-valued
attributes, and allows various corrective actions to be taken rather
than aborting. This allows for cardinality mistakes to be "fixed" in a
predictable way, and can also be used to construct single-valued
attributes from multi-valued ones.

* Fix typo

* Fix tests

* Added Dutch translations

* Fix phpdoc

* Whitespace fixes

This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com

* Fix typo in fixing typo

This commit consists of patches automatically generated for this project on https://scrutinizer-ci.com