Create a linuxcnc python package

[hdiethelm]

Linuxcnc spams the shared python namespace if installed:

/usr/lib/python3/dist-packages/raster.py
/usr/lib/python3/dist-packages/preview_helpers.py
/usr/lib/python3/dist-packages/propertywindow.py
/usr/lib/python3/dist-packages/pyhal.py
/usr/lib/python3/dist-packages/pyngcgui.py
/usr/lib/python3/dist-packages/hal.py
/usr/lib/python3/dist-packages/hal_glib.py
/usr/lib/python3/dist-packages/hershey.py
/usr/lib/python3/dist-packages/lineardeltakins.cpython-313-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/linux_event.py
/usr/lib/python3/dist-packages/linuxcnc.cpython-313-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/linuxcnc_util.py
/usr/lib/python3/dist-packages/multifilebuilder.py
/usr/lib/python3/dist-packages/common
...

This has the risk for collisions with other packages and is generally not a good practice.

It would be better to create a lcnc or linuxcnc package.

Discussion started here: #4132

[BsAtHome]

pyhal.py will be retired. Everything else should move into a proper namespace. I'd suggest linuxcnc, like I introduced in C++, and move everything into it. There may be some fiddling for some parts because we need to consider which parts can be run/imported without instantiating a whole infrastructure.

Another question is when this breaking change should be done.

[hdiethelm]

+1 for linuxcnc
lcnc is a bit short and has more potential for conflicts

It will be breaking for every external python part because you have to change for example form import hal to from linuxcnc import hal. Not a big deal for programmers but for other people, it might be annoying.

[grandixximo]

Should have a deprecation period, I thought I posted here
+1 for linuxcnc