Support eZ publish attributes in dump()

This extracts eZ publish attributes, which are normally used in templates, as virtual attributes in the dump() function. This is done by using the Casters system in var-dumper.

There are now also extra configuration entries for defining casters and controlling virtual attributes.

See README.md for more details.

v1.13.1: Allow Sentry release project to be set

Set project by adding this to the config:

[
    'sentry' => [
        'project' => 'my-project',
    ],
]

All releases sent to Sentry will then be prefixed with my-project@.

v1.13: Sentry fixes

• Expose bootstrap_describe and bootstrap_test_sentry as scripts
• Sentry fixes:
  • Made setupSentry static as it is called that way
  • Protected against ezpEvent usage when it does not exist, for instance if used outside eZ publish
  • Made sure user info is merged
  • Set environment information
  • Set release information from git
  • Enable stack traces for non-exceptions

v.12.3: Control configs using env variables.

Support for using env variables to control the various configuration which are loaded.

The env variables are:

• BASE_CONFIGS
• FRAMEWORK
• APP_ENV
• EXTRA_CONFIGS

v1.12.2: Bugfixes and support for describing all changes.

• Added a way to describe the changes to the system, use binary bootstrap_describe.
• Don't log var-dumper entries too early
• Fixed check for env variable USE_DOCKER
• Changed define EZP_USE_FILE_PERMISSIONS into a global variable

v1.12.1: Bugfixes for sentry support

• Added script to test Sentry config
• Fixed bug in Sentry logger when no URI is used

v1.12.0: Fixed support for Sentry SDK 2.x

If the API is detected it installs the default log handler which
now uses the 2.x SDK, otherwise it tries the 1.x API.

New features

• Report more details from eZ publish as tags. This includes
  eZ publish version, logged in user, route/module details,
  request url, site access and locale.
• Reporting of eZ publish events, defaults to navigation and some
  session events.

v1.11.6

No longer require sentry package.
The sentry package should be installed in the project itself which can control the exact version it needs.
Added sentry/sentry as a suggestion.

v1.11.2

Fixes to Whoops error handling

• Only use custom var dumper if Whoops 2+ is used
• Avoid throwing exceptions in log setup
  This avoids disrupting the callers code base due to incorrect
  configuration or if the channel simply is not defined.
• Channels site and base are logged to var/log for ezp apps
• Catch exceptions in bootstrapping of Whoops error handler

v1.11.1: Fixed VarDump problem for non-dev installs.

• Fixed issue with error report on prod, it tried to use the class
  \Symfony\Component\VarDumper\Cloner\VarCloner which only exists
  in dev mode.