Split monorepo by operational component

[jgafnea]

It may be worth considering splitting the current monorepo along operations boundaries. This would reduce dependencies between components with different deployment targets and update frequency, simplifying installation, maintenance, and ongoing development.

Proposed structure:

openrvdas-daq         # shipboard data acquisition
openrvdas-operations  # alerting and dashboards
openrvdas-website     # Python backend and JavaScript frontend
openrvdas-shared      # common utilities and reusable components

This approach would directly benefit most of the current issues, including:

• Investigate/implement packaging of OpenRVDAS in pyproject.toml #498
• Refactoring webUI frontend/backend to better support improvements like those demo'ed by NCMI #503

Names and exact boundaries are open, but the goal is to separate major components to simplify existing and future work.

[webbpinner]

I'm going to suggest openrvdas-daq vs openrvdas-vessel as OpenRVDAS is used on other platforms like ROV, AUV, polar land sensors and Pablo's greenhouse.