Add github workflow to automatically update pixi lockfile

[xela-95]

In this way, we do not risk forgetting to maintain the Pixi lock files.

The action comes from the official documentation: https://pixi.sh/dev/advanced/updates_github_actions/#how-to-use with some customizations done by @flferretti in https://github.com/ami-iit/jaxsim/pull/221

Remark: as specified in the documentation, the permission of the repo should be set as follows:

[xela-95]

Triggered the action on my fork of the repository since the action is only available when on main: https://github.com/xela-95/gz-sim-yarp-plugins/actions/runs/10724133024

[xela-95]

Triggered the action on my fork of the repository since the action is only available when on main: https://github.com/xela-95/gz-sim-yarp-plugins/actions/runs/10724133024

It executed successfully and it generated the PR: https://github.com/xela-95/gz-sim-yarp-plugins/pull/1

[traversaro]

I am not enthusiastic of the idea of the automatic pixi-lock update (for the reasons described in https://github.com/robotology/whole-body-estimators/pull/191), but if it is happening only one a month that is ok for me.

[xela-95]

I am not enthusiastic of the idea of the automatic pixi-lock update (for the reasons described in robotology/whole-body-estimators#191), but if it is happening only one a month that is ok for me.

Thanks for linking the discussion, I've not considered that side-effect, maybe we could track the pixi lockfile with LFS or maybe only maintain the the manual worflow-dispatch way of running the action.

[traversaro]

I think we can try the automatic update for some time and then monitor the size of the repo. If it increases too much, we can switch to manual sporadic updates.

[xela-95]

Perfect! Merging 🚀