Add inclusive naming workflow

[sed-i]

Description

Currently, o11y CI fails for inclusive naming in this lib.
This PR addresses those issues and introduces an inclusive naming workflow.

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation.
• I have added tests that validate the behaviour of the software.
• I validated that new and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.
• I have bumped the version of any required library.

[gruyaume]

I don't think a project's CI should fail because one of its dependency doesn't follow the same coding standards (linting, inclusive naming, etc.) In other words, why don't you make the change in your project to only scan for its source code (and ignore the third party libs).

[saltiyazan]

Can that really happen? Why would the ci of a project using this lib fail if doesn't follow the same rules and coding standards? it has it's own ci at the end of the day.

[sed-i]

Closing for now, as we can utilize inline ignores and .wokeignore.