Deprecate incorporated libraries

[RobPasMue]

As a result of this package we have incorporated several smaller libraries into a single one:

• ansys-tools-path
• pyansys-tools-versioning
• pyansys-tools-report
• ansys-tools-local-product-launcher

We should probably deprecate them officially and create a last version on all of them that import the ansys-tools-common project, and throw a warning inviting users to migrate to the new lib

[RobPasMue]

Now that the library has been officially released, we should start deprecating the other packages:

• Submit a PR to each of them where we remove all the source code file for these repos and we depend directly on the ansys-tools-common package
• Implement imports at the same level - for example:

In https://github.com/ansys/pyansys-tools-report/blob/main/src/ansys/tools/report/__init__.py, instead of

"""PyAnsys Tools Report package."""

# Improving accessibility to the pyansys-tools-report resources

from ansys.tools.report._version import __version__, version
from ansys.tools.report.report import Report

Something like

"""PyAnsys Tools Report package."""

# Improving accessibility to the pyansys-tools-report resources

from ansys.tools.report._version import __version__, version
from ansys.tools.common.report import Report

# Throw a warning saying that this project is deprecated and will no longer be updated + 
# the fact that users should migrate to the new package imports

• Do not pin down a specific version of ansys-tools-common -- just leave it free
• Make a new minor release with these changes

Overall, follow the deprecation library process in https://dev.docs.pyansys.com/how-to/deprecating.html#deprecating-a-library but with the added functionality of "reimporting" the ansys-tools-common package as needed. We can discuss this offline if you have any doubts @AlejandroFernandezLuces

[AlejandroFernandezLuces]

I do not have permissions to archive pyansys-tools-report, but it is ready to be archived.