While it might be useful for later stages in development, let's keep this simple

It's used by symfony, use API_ instead

This mainly means the keycloak config moves to a separate bundle

chore(deps): lock file maintenance

See merge request dbp/dbp-api/api-server-template!29

there is no group named "api", there is only "rest" for non-app
specific tests

The core bundle is now available on packagist

While the starter bundle gives a nice example for how to integrate an API
it makes setting up a new server harder because the user usually already
has a bundle in mind that he/she wants to add.

So remove it and instead make it easier to add bundles by improving the docs

This is now handled by the composer.json in .gitlab-ci if needed

Users shouldn't need to care about this

chore(deps): lock file maintenance

See merge request dbp/dbp-api/api-server-template!28

chore(deps): update dependency phpstan/phpstan-phpunit to v0.12.21

See merge request dbp/dbp-api/api-server-template!27

chore(deps): lock file maintenance

See merge request dbp/dbp-api/api-server-template!26

chore(deps): update dependency phpstan/phpstan to v0.12.92

See merge request dbp/dbp-api/api-server-template!25

symfony now requires framework.secret to be set
the person entity is gone from the core bundle, so no need to implement it.

fix(deps): update dependency symfony/framework-bundle to v5.3.3

See merge request dbp/dbp-api/api-server-template!24

chore(deps): update all non-major dependencies (patch)

See merge request dbp/dbp-api/api-server-template!23

fix(deps): update all non-major dependencies (patch)

See merge request dbp/dbp-api/api-server-template!22

chore(deps): update all non-major dependencies (patch)

See merge request dbp/dbp-api/api-server-template!21