[#460] Add dev_permission flag to bazel

[elBoberido]

Notes for Reviewer

1. Permissions are used to manage access to shared memory objects on the file system used by iceoryx2
2. In a docker environment, the user permissions on the host are not aligned with that within the container environment
3. A dev_permissions feature flag has been added, allowing all processes access to all shared memory objects to allow usage in the docker environment
4. This PR adds the dev_permissions feature flag to the bazel build

Pre-Review Checklist for the PR Author

1. Add sensible notes for the reviewer
2. PR title is short, expressive and meaningful
3. Relevant issues are linked in the References section
4. Every source code file has a copyright header with SPDX-License-Identifier: Apache-2.0 OR MIT
5. Branch follows the naming format (iox2-123-introduce-posix-ipc-example)
6. Commits messages are according to this guideline
   • Commit messages have the issue ID ([#123] Add posix ipc example)
   • Commit author matches Eclipse Contributor Agreement (and ECA is signed)
7. Tests follow the best practice for testing
8. Changelog updated in the unreleased section including API breaking changes
9. Assign PR to reviewer
10. All checks have passed (except task-list-completed)

Checklist for the PR Reviewer

• Commits are properly organized and messages are according to the guideline
• Unit tests have been written for new behavior
• Public API is documented
• PR title describes the changes

Post-review Checklist for the PR Author

1. All open points are addressed and tracked via issues

References

Relates to #460

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.12%. Comparing base (a48cd97) to head (2d27b26).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #467      +/-   ##
==========================================
- Coverage   79.21%   79.12%   -0.09%     
==========================================
  Files         196      196              
  Lines       23538    23538              
==========================================
- Hits        18646    18625      -21     
- Misses       4892     4913      +21     

see 8 files with indirect coverage changes

[orecham]

Suggested change

	build options.These flags allow you to enable or disable specific features
	build options. These flags allow you to enable or disable specific features

[orecham]

Also some other issues the linter would catch. Did you install an auto-formatter?

[elBoberido]

Is it part of a git hook?

[orecham]

@elBoberido No but am not so sure if it is a good idea for that. Ideally the auto-corrections should be verified quickly (either with a git diff or in-editor with an auto formatter). There is this script the fixing from the terminal: https://github.com/eclipse-iceoryx/iceoryx2/blob/main/internal/scripts/check_markdown_linting.sh

[elBoberido]

@orecham I know that script but forgot to run it. I'll create a git hook to run it on all markdown files in the commit if the markdown linter is available. That should be fairly fast and catches the issues immediately for regular contributors.

[orecham]

@elBoberido If you want to do that, the script should already take care of finding the files on the current branch (including those not committed), so the hook would only need to run the script.

The hesitation I have is the time it takes (could be too long for a hook) and the line length correction which can mess up some intentional formatting.

Feel free to change the script however you want though.

[elBoberido]

The hook would only do the check, not perform any changes. That would be up to the developer to trigger.