It yielded a yaml syntax error

* Reinstate url-based authentication

* Add some unit tests

* Fix legacy url

* Fix typo

* Drop code related to legacy discojuice-module

Closes: #1759

Co-authored-by: Marko Ivančić <marko.ivancic@srce.hr>

The endpoint-change was made backwards-compatible

They only serve purpose in Github Actions

* fix: tarball extracted in current directory

* Cleanup composer-file

---------

Co-authored-by: Tim van Dijen <tvdijen@gmail.com>

It is quite fine if e.g. a theme does not have its own locales dir.
The exception is already caught, so the application does not actually
stop. So, notice it but do not raise high alarms.

* Fix missing state parameter

* Slightly rationalize naming convention for selectors

* Add RequestedAuthnContextSelector

* Allow source-selector to return multiple sources

* Fix docs

* Revert return-type change

* Throw exception for incomplete config

* Remove test-data for non-implemented cases

* Codesniffer fix

* Move www > public

* Remove local assets

* Import remotely generated assets

* Update files to reflect www > public move

* Update upgrade notes

* Make assets-filter aware of new assets-location

* Update test-framework

* Exclude generated assets from code sniffer

- Fix several bugs to make it actually work.
- Simplify code a lot.
- Move presentation concerns to the template and use standard
  functionaliy for translation.

A small change needed to be made in the name of the css_class
setting (previously css-class) in the name of simplicity.

The old format has been replaced with a new format in SSP 1.9. The new format makes sense and it's now time to stop supporting the legacy format.

Previously, (just) a warning would be logged as
"Error 2 - something"
"Error 8192 - use of thing is deprecated"

Now this is logged as
"Warning - something"
"Deprecated - use of thing is deprecated"

This should avoid red herrings when debugging an issue when e.g. a
warning, notice or even deprecation notice looks like its an
actual error while it's not.