Query About Repository Structure

# QwikContext
I'm not clear on why the Wheel for `omsdk` includes `omdrivers` rather than depending on it and would appreciate some clarification please.

# Details
Apologies if this isn't the correct place to raise this, but I haven't been able to figure it out on my own. I'm currently attempting to package `omsdk` for Fedora (and by extension, RHEL), but I'm running into issues with the way this repo is laid out. Could you please explain why `omsdk` bundles `omdrivers` into its wheel, rather than depending on it?

I've got a Fedora-friendly RPM for `omdrivers`, and am trying to make one for `omsdk`, but don't think I can without unpicking the two modules.

This does also mean that if you `pip install omsdk omdrivers`, then you will end up with duplicate installs.

# Repro Steps
N/A

# Impact
I am very confused.

# NeedBy
When convenient.

# Severity
Low.

No file or test is named. Start by inspecting the packaging metadata and the built wheel to trace how omdrivers enters omsdk; done means documenting the bundling rationale and the implications for Fedora and RHEL packaging.

Written by the indexing model from the issue text.