Do a tag and release in PyPI and conda-forge

[traversaro]

For managing dependencies in comodo, it may be convenient to release this package in PyPI and then conda-forge. This is something I can prepare the PR for, or if you have time I can help anyone to work on.

In particular we need to:

• S1: Rename repository to amo-urdf: not compulsory, but good to align the repo with the rest of organization and the PyPI and conda-forge naming conventions, having the python package be name something-something and the Python module something_something is quite classical, even if it is counterintuitive at first, see for example https://github.com/Farama-Foundation/Gymnasium-Robotics/blob/27147610f230f49236cf376a7f08cceac917efe9/pyproject.toml#L8 and https://github.com/Farama-Foundation/Gymnasium-Robotics/tree/27147610f230f49236cf376a7f08cceac917efe9/gymnasium_robotics.
• S2: Prepare for PyPI upload: You can first add an action like https://github.com/ami-iit/resolve-robotics-uri-py/blob/main/.github/workflows/publish-to-pypi.yml to your repo, and then register on PyPI, and then add the github action that you added by following the guide in https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/ .
• S3: Once you do that, add a release/tag to your project, and it will automatically uploaded also to PyPI.
• S4: Once your problem is on PyPI, you can create a conda recipe with grayskull (like https://github.com/conda/grayskull), and then add it in conda-forge with a PR to staged-recipes (see https://conda-forge.org/docs/maintainer/understanding_conda_forge/staged_recipes/).

[traversaro]

(by the way, while writing this list I realized that it could be useful to document this in https://github.com/ami-iit/ami-commons . https://www.pyopensci.org/python-package-guide/tutorials/publish-pypi.html and https://www.pyopensci.org/python-package-guide/tutorials/publish-conda-forge.html are useful references, but probably a self-contained document targeting AMI members could be useful).