Refactor dynamic routing package

[mekhlakapoor]

User story

As a developer, I want the packages to be separated by acquisition machine and for them to all follow the same general structure. Refactor the dynamic routing package to be separated

Acceptance criteria

• Separate dynamic routing into each of their own packages.
• Each of the packages should have a JobSettings class
• Replace test_utils with module actually testing utils module in package (currently its just utils for the tests)

Sprint Ready Checklist

• 1. Acceptance criteria defined
• 2. Team understands acceptance criteria
• 3. Team has defined solution / steps to satisfy acceptance criteria
• 4. Acceptance criteria is verifiable / testable
• 5. External / 3rd Party dependencies identified
• 6. Ticket is prioritized and sized

Notes

• We need to clarify what the difference is between mvr_rig, neuropixels_rig, and sync_rig.
• Look at bergamo package as an example for JobSettings