Improved reporting on shared build services with same FQCN but different class

[Vampire]

Expected Behavior

It happens regularly that questions come up like

Cannot set the value of task ':grpc:stub:python:checkPython' property 'envService' of type ru.vyarus.gradle.plugin.python.service.EnvService using a provider of type ru.vyarus.gradle.plugin.python.service.EnvService.

This is typically caused by a plugin being applied to two sibling projects and then using a shared build service.
The first project register the service, the second gets the previous registration but receives an instance of the class on the other class loader so cannot use the service.

It would be nice if on getting a service, and / or setting a provider, and the expected and actual type are not equal but have the same FQCN, a more actionable message is presented like "add the plugin with problem with apply false to the root build script" or something similar.

[ghale]

The issue is in the backlog of the relevant team and is prioritized by them.