App pollutes global namespaces with dev deps

Steps to reproduce

1. Install the app on a dev env

Expected behaviour

Installation stays clean

Actual behaviour

Dev tools pollute the rest of the installation. Some dev tools even have conflicts with each other (nextcloud/ocp and vimeo/psalm for example need different versions of psr/container).

https://docs.nextcloud.com/server/latest/developer_manual/app_development/dependency_management.html#development-tools explains how this can be fixed easily.

Server configuration

Operating system:

Web server:

Database:

PHP version:

Nextcloud version: (see Nextcloud admin page)

Where did you install Nextcloud from:

Signing status:

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Nextcloud configuration:

If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder

or

Insert your config.php content here
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...

Client configuration

Browser:

Operating system:

Logs

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...

@artonge @miaulalala

Reproduce the issue by installing the Activity app in a development environment, then read the linked Nextcloud dependency-management guidance. Done means development tools no longer pollute the rest of the installation and the reported dependency-version conflict is resolved.