Remove glpi tools dep

[froozeify]

GLPI tools is now natively inside GLPI 11 core, we can remove it's dependency.

Based on what was done on the whatsapp plugin, I've updated the autoload and test bootstrap.

Nightly images will run it and otherwise it will be available on GLPI 11.0.6

Interconnected PR (merge order) :

• Fix common dependencies check exception when composer.json has no dependencies glpi-project/plugin-ci-workflows#50
• Migrate glpi-project/tools to core glpi-project/glpi#22465
• Remove glpi tools dep #57

[trasher]

GLPI tools is now natively inside GLPI 11 core, we can remove it's dependency.

GLPI tools is not included in GLPI, that's still something to be done.

[froozeify]

My mistake this one should be in draft until glpi-project/glpi#22465 is merged. I put it in the interconnect merge order but forgot to flat this as draft for now.

Edit could still be checked but only merged by following the order (and after glpi release)

Looks like I can't change the status from GitHub Mobile app

[Rom1-B]

Throwing an exception seems better than die()?

Suggested change

	$current_plugin_folder = basename(realpath(__DIR__ . '/../'));
	require __DIR__ . '/../../../tests/bootstrap.php';
	require dirname(__DIR__) . '/vendor/autoload.php';
	if (!Plugin::isPluginActive("{LNAME}")) {
	throw new RuntimeException("Plugin {LNAME} is not active in the test database");
	if (!Plugin::isPluginActive($current_plugin_folder)) {
	echo("Plugin $current_plugin_folder is not active in the test database" . PHP_EOL);
	die();
	require __DIR__ . '/../../../tests/bootstrap.php';
	require dirname(__DIR__) . '/vendor/autoload.php';
	if (!Plugin::isPluginActive("{LNAME}")) {
	throw new RuntimeException("Plugin {LNAME} is not active in the test database");

[trasher]

Far better, yes. Also die() returns 0; which is not an error.