[FEA]: Add check to CI to detect incorrect imports of morpheus._lib modules

[mdemoret-nv]

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

Imports of morpheus._lib should be used very rarely and will follow a specific format when used correctly. Sometimes tools like VS Code can auto add imports to the morpheus._lib module when a similar name is used in morpheus. For example, from morpheus._lib.messages import MessageMeta should really be from morpheus.messages import MessageMeta which will auto select the correct class depending on whether C++ is enabled or not.

Describe your ideal solution

Since we should never be using from morpheus._lib.XXX import YYY it should be easy to detect in CI any incorrect uses. The following is a list of the rules:

• Ban: from morpheus._lib.XXX import YYY
  • Instead, it should be from morpheus.XXX import YYY to pick the correct C++/Python version
  • This may require re-exporting the C++ symbols in an __init__.py
• Ban: import morpheus._lib.XXX
  • Instead, it should be import morpheus.XXX
• Ban: import morpheus._lib.XXX as YYY
  • Instead, it should be import morpheus.XXX as YYY
• Allow: import morpheus._lib.XXX as _XXX
  • This is the only way that C++ modules should be imported.
  • It should be redefined as a new name to prevent accidental re-export
  • Most of the stages follow this format already

Describe any alternatives you have considered

Looked for ways to prevent the auto importer in VSCode from using morpheus._lib, but it doesnt seem possible.

Additional context

This recently broke the SID Visualization example in 23.01.00

Code of Conduct

• I agree to follow this project's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request