docs: clarify container command wrapper workflows

[gcomneno]

Summary

Document advanced bitbake.commandWrapper workflows for container-based setups.

This adds examples for:

• forwarding generated BitBake commands into an already-running container with docker exec
• passing generated commands through a wrapper script into a Makefile target
• keeping configured paths valid from the environment where the wrapped command runs
• making wrapper scripts executable

Validation

• git diff --check
• npm run lint

[gcomneno]

This documentation update is intended to capture the currently documented workaround direction for advanced container setups discussed in issues like #450, #415, and #416.

I avoided changing runtime behavior here and kept the PR focused on commandWrapper wrapper-script patterns for already-running containers and Makefile-driven environments.

[deribaucourt]

I don't think this documentation is part of the scope of this extension. The extension doesn't provide guidance on executing Yocto within a reproducible docker or scripted environment. Since many users do, we provide features to integrate with it, but we don't aim to help people set it up. Several technologies exist, but the only official one is oe-init-build-env, which is the default and most documented approach for our settings.

The only responsibility of this extension is to document how to configure it for docker for the users who will need it. I think the current wrappers cover the most common use cases allready.

Also we absolutely won't recommend invoking bitbake under Makefile. Please don't do this. Users who unfortunately inherited from such a setup can refer to some issues discussions which describe possible approaches like this one.

So far I'm not convinced in keeping any of this PR for the reasons above. Do you identify a particular lack of documentation that would fall in the scope described above

[gcomneno]

Thanks for the clear scope boundary.

That makes sense. I’ll close this PR rather than keep pushing documentation that goes beyond the extension’s responsibility.

For future documentation contributions, I’ll keep the focus on how to configure extension features themselves, rather than guidance for setting up Yocto/container/Makefile-based environments.