Fix Bzlmod module name typo

[lalten]

Notes for Reviewer

Currently if you want to depend on Iceoryx as a Bzlmod bazel_dep you have to do something like

bazel_dep(name = "org_eclipse_iceroyx", repo_name = "iceoryx")
git_override(
    module_name = "org_eclipse_iceroyx",
    commit = "00c5349eabfb1bce5db46efefb39fd9471679be1",
    patches = ["//third_party/iceoryx:iceoryx.patch"],
    remote = "https://github.com/eclipse-iceoryx/iceoryx",
)

It would be nice to fix that typo.

I'll send some follow up PRs to contribute patches that make depending on the module via Bzlmod actually work.

Pre-Review Checklist for the PR Author

1. Code follows the coding style of CONTRIBUTING.md
2. Tests follow the best practice for testing
3. Changelog updated in the unreleased section including API breaking changes
4. Branch follows the naming format (iox-123-this-is-a-branch)
5. Commits messages are according to this guideline
   • Commit messages have the issue ID (iox-#123 commit text)
   • Commit author matches Eclipse Contributor Agreement (and ECA is signed)
6. Update the PR title
   • Follow the same conventions as for commit messages
   • Link to the relevant issue
7. Relevant issues are linked
8. Add sensible notes for the reviewer
9. All checks have passed (except task-list-completed)
10. Assign PR to reviewer

Checklist for the PR Reviewer

• Consider a second reviewer for complex new features or larger refactorings
• Commits are properly organized and messages are according to the guideline
• Code according to our coding style and naming conventions
• Unit tests have been written for new behavior
• Public API changes are documented via doxygen
• Copyright owner are updated in the changed files
• All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
• PR title describes the changes

Post-review Checklist for the PR Author

1. All open points are addressed and tracked via issues

References

• Closes Fix Bazel Typo #2364

[elfenpiff]

@lalten Thanks for the contribution. Since we are an open source project under the eclipse foundation you need to sign the ECA: https://www.eclipse.org/legal/eca/

We are targeting mission-critical systems and this requires that every change in the repo must be connected to an issue. So could you please create an issue.

Also every commit must have the prefix iox-#??? where ??? is the issue number.

[lalten]

@elfenpiff please have another look.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.69%. Comparing base (05959a1) to head (cc1cf75).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2363      +/-   ##
==========================================
+ Coverage   78.32%   78.69%   +0.36%     
==========================================
  Files         440      440              
  Lines       16186    16981     +795     
  Branches     2314     2361      +47     
==========================================
+ Hits        12678    13363     +685     
- Misses       2658     2736      +78     
- Partials      850      882      +32     

Flag	Coverage Δ
unittests	78.49% <ø> (+0.33%)	⬆️
unittests_timing	15.35% <ø> (+0.30%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 174 files with indirect coverage changes

[elfenpiff]

@lalten Looks good. I created this issue #2364 for you. Could you please adjust your commit message so that the prefix is iox-#2364 - then we can merge this PR.