fix: resolve wheel build collisions by refining package paths

[BenjPetr]

Signed-off-by: Benjamin Petrick 170433522+BenjPetr@users.noreply.github.com

Checklist

Please check if the PR fulfills these requirements:

• PR Title follows conventional commit messages
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• All commits in this PR are DCO signed-off (see CONTRIBUTING.md)

Does this PR already have an issue describing the problem?

No

What is the new behavior (if this is a feature change)?

This PR corrects the pyproject.toml configuration to prevent build failures during wheel creation. It explicitly maps each sub-package to its specific source directory instead of the generic src parent folders.

Changes:

Fixed Build Failure: Resolved a ValueError where multiple src/init.py files were colliding in the wheel archive.
Improved Distribution: Restricted the bundled files to only the intended toop_engine_* packages, automatically excluding auxiliary scripts (like compile_proto.sh) and boilerplate files located in the src roots.
Backend Optimization: Standardized the Hatch build target configuration to ensure reliable installations across all modules.

Does this PR introduce a breaking change?

• Yes
• No

[Copilot]

Pull request overview

This PR updates the root Hatch wheel-build configuration to avoid file collisions during monorepo wheel creation by scoping the wheel’s included packages to the concrete toop_engine_* package directories (instead of each package’s generic src/ root).

Changes:

• Refines [tool.hatch.build.targets.wheel].packages to point at packages/*_pkg/src/toop_engine_* directories explicitly.
• Prevents accidental inclusion of non-package root files (e.g., src/__init__.py, helper scripts) that can collide or be unintentionally bundled.

[sonarqube-mccs]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube