feat(ros): additional package maps

[daenny]

This allows for an additional key in the package.build.config:

extra-package-mappings = ['path-to-file.yaml']

This will add/overwrite the mappings from robostack e.g. if you host your own packages.

An additional (later) option would be to let packages allow to install the mapping file inside the build environment.

I also added a test enviroment to the pixi.toml such that it is easy to develop and test within pycharm.

You can now open a pycharm session inside the pixi-build-ros test environment and select the correct interpreter. Then you can run the pytest within pycharm.

[baszalmstra]

Partial review, love the functionality

[daenny]

Some additions:

• I renamed robostack to conda in the packagemap that feels more descriptive. WDYT?
• I also added the option to define rosdistro packages in the package map, which are resolved using the same rules as if it is defined in the rosdistro.

[baszalmstra]

Im not sure about the robostacknto conda rename. It makes it slightly harder to migrate from the robostack based file. Can we instead allow both keys and not rename the keys in the bundled file?

I would also prefer to create seperate PRs for these changes because this PR is already becoming very large.

[tdejager]

Might also be nice to have a follow-up PR to be able to create the mapping inline. I was discussing this with someone in the prefix.dev robotics discord. It also makes it easier to create a stand-alone example or test :)

[nichmor]

hey! I've tested the PR, and it works as expected!
The only thing that I would like to ask is if I set the new field in the navigator package ( from ros_work), like this:

and will try to build it like this:
PIXI_BUILD_BACKEND_OVERRIDE_ALL=1 pixi build
It can still build it without errors ( I would expect an error because path-to-file.yaml doesn't exist ) .

Is it expected?
If yes, we can merge it

[daenny]

@nichmor thanks for the review. I had that as intended behaviour, but indeed it might be confusing. Now I throw an value error.
I also fixed the double symlink in the noetic build script.

[nichmor]

@nichmor thanks for the review. I had that as intended behaviour, but indeed it might be confusing. Now I throw an value error. I also fixed the double symlink in the noetic build script.

thanks! let me retry it, and I think we can merge it after that

[nichmor]

works as expected, thanks a lot!